Turn dist_plone into an egg and show how the installers can share this egg

[GoogleCodeExporter]

In the Plone repository (http://dev.plone.org/plone/browser/Installers), there 
is a "dist_plone" 
package which is used to manage which packages make up a Plone release. The 
installers currently 
use this.

The task: Turn dist_plone into an egg and verify that its API is suitable to be 
called from any 
package. With this, we can release a dist_plone egg to the Python Package Index 
for each Plone 
release. The various installers could then fetch this egg to determine how to 
install a particular 
version of Plone, rather than rely on manually copying files or using 
svn:externals as we do 
currently.

For bonus points, create a new version of the "plone.recipe.plone" buildout 
recipe that uses this 
egg.

Original issue reported on code.google.com by optil...@gmail.com on 19 Nov 2007 at 11:24

[GoogleCodeExporter]

Original comment by l...@gmail.com on 27 Nov 2007 at 7:09

• Changed state: Open
• Added labels: 3-day

[GoogleCodeExporter]

Original comment by mw4...@googlemail.com on 23 Jan 2008 at 11:36

• Changed state: deleted