Ross Patterson wrote:
I often end up doing development on the same distribution for multiple
projects and have long wished for a simple way to share the same
clone/checkout between these multiple buildouts.
What would you think about supporting a shared sources directory much in
the same vein of zc.buildout's use of eggs-directory, zc.recipe.cmmi's
use of download-cache, and plone.recipe.zope2install's use of
zope-directory all of which can be set in the users
~/.buildout/default.cfg?
If the option is set, we could do the clone/checkout into the shared
sources directory and then symlink them into sources-dir.
+1, but as wichert said, it should be overridable per develop egg.
Also, with symlinking, supporting Windows is hard (though not impossible
with junction.exe). Just make sure it's not a hard requirement to use
symlinks/this feature.
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
