On Nov 15, 2008, at 8:28 AM, Chris Withers wrote:
Hi All,
I'm getting a growing number of customer-specific and non-open- source eggs. I used to just put these in as svn:externals and then add the path in as a develop egg, however, I'm not sure this is going to scale.
What I'd like to do is have a "local egg repository" that I can put these eggs in and then just point buildout at it.
Has anyone done this before?
Yes
Failing that, is there any way in buildout to say "use this egg repository in favour of pypi, and only look at pypi if the egg isn't found in the local repository"?
Just set up a flat directory somewhere and tell buildout (or any other setuptools-based software, like easy_install) to add it to its list of find links. A repository doesn't have to be a formal index. We simply set up an sftp server and point buildout at it using the buildoutsftp buildout extension and sftp urls, as in: extensions = zc.buildoutsftp find-links = sftp://private.zope.com/private This provides restricted access with authentication using ssh keys. Jim -- Jim Fulton Zope Corporation