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?
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"?
Also, does anyone have any software that makes a good egg repository?
Does anyone have anything that supports the equivalent of:
python setup.py upload
...but to a local repository?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
