[Grok-dev] the installation problems saga, part 2

Christian Theune ct at gocept.com
Thu Apr 24 00:56:12 EDT 2008

On Thu, Apr 24, 2008 at 01:57:32AM +0200, Martijn Faassen wrote:
> Perhaps this is a direction to explore: we could write a tool that for a  
> given package downloads all the right versions of the dependencies (as  
> we specify somewhere), and then packages them up in some form of special  
> tarball that contains the package and all its dependencies. We then also  
> have a tool which can find these big balls somewhere and installs them  
> into a place on the user's filesystem where buildout can find them as  
> normal eggs. Unfortunately I can't think of a way to fit this into the  
> whole setuptools/eggs system, and it'd be a bother to have to step  
> outside it - it'd be nice if setuptools looked for these balls first if  
> it saw a dependency in setup.py, and will get it first.

I haven't used it, but have a look at zc.sourcerelease which supposedly should
do something along this lines for buildouts in general.


gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development

More information about the Grok-dev mailing list