Comments on: Poaching (Patching) Eggs http://shane.willowrise.com/archives/poaching-patching-eggs/ Tech Notes from Shane Hathaway Wed, 04 Aug 2010 23:57:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: David Glick http://shane.willowrise.com/archives/poaching-patching-eggs/comment-page-1/#comment-985 David Glick Fri, 16 Jan 2009 23:53:01 +0000 http://shane.willowrise.com/?p=70#comment-985 Haha, that's really funny that you named your version omelette too without knowing about mine. Feel free to contribute to collective.recipe.omelette :) Haha, that’s really funny that you named your version omelette too without knowing about mine. Feel free to contribute to collective.recipe.omelette :)

]]> By: Ian Bicking http://shane.willowrise.com/archives/poaching-patching-eggs/comment-page-1/#comment-984 Ian Bicking Fri, 16 Jan 2009 22:08:00 +0000 http://shane.willowrise.com/?p=70#comment-984 I'm inclined to approach this slightly differently. First, there's no good way to deal with branches with our current systems. There's a sense of a single timeline of the package, and you either have a newer version or an older version, you can't have a sideways version. So first I'd like a clear way to talk about a sideways version. From there, maybe the sideways version could be maintained as a patch with a simple stub of a setup.py. The setup.py could mostly proxy to the "real" setup.py (the upstream package) then apply patches after installation. The one issue I'm not sure about is how to handle getting the upstream package. Do you distribute the whole thing? Could you recursively call out to the installer? Well, distributing the upstream version with the patches is clearly the easiest. I’m inclined to approach this slightly differently. First, there’s no good way to deal with branches with our current systems. There’s a sense of a single timeline of the package, and you either have a newer version or an older version, you can’t have a sideways version. So first I’d like a clear way to talk about a sideways version.

From there, maybe the sideways version could be maintained as a patch with a simple stub of a setup.py. The setup.py could mostly proxy to the “real” setup.py (the upstream package) then apply patches after installation. The one issue I’m not sure about is how to handle getting the upstream package. Do you distribute the whole thing? Could you recursively call out to the installer? Well, distributing the upstream version with the patches is clearly the easiest.

]]> By: Florian Schulze http://shane.willowrise.com/archives/poaching-patching-eggs/comment-page-1/#comment-983 Florian Schulze Fri, 16 Jan 2009 10:12:42 +0000 http://shane.willowrise.com/?p=70#comment-983 The omelette recipe is still missing zip unpacking. Feel free to add that :) The omelette recipe is still missing zip unpacking. Feel free to add that :)

]]> By: Shane Hathaway http://shane.willowrise.com/archives/poaching-patching-eggs/comment-page-1/#comment-976 Shane Hathaway Fri, 16 Jan 2009 05:09:44 +0000 http://shane.willowrise.com/?p=70#comment-976 Eggcellent, thanks! I'm glad I don't have to maintain it after all. :-) Eggcellent, thanks! I’m glad I don’t have to maintain it after all. :-)

]]> By: Martijn Faassen http://shane.willowrise.com/archives/poaching-patching-eggs/comment-page-1/#comment-972 Martijn Faassen Fri, 16 Jan 2009 02:54:22 +0000 http://shane.willowrise.com/?p=70#comment-972 Have you seen the already pre-existing Omelette buildout recipe which does the same thing? http://pypi.python.org/pypi/collective.recipe.omelette Have you seen the already pre-existing Omelette buildout recipe which does the same thing?

http://pypi.python.org/pypi/co.....e.omelette

]]>