[Distutils] setuptools 0.6c7 and zc.buildout: find-links egg fragment issue

[Tarek Ziadé]

Jim Fulton wrote:
> 
>>
>> Ok. The use case is : we are working on a bunch of private packages
>> that do not have a public distribution.
> 
> Have you considered a private repository?
> 

It is in a private repository.


Jim Fulton wrote:
> 
>> Then we create for each package a tag on the svn. And we want to
>> distribute our buildout. so we change the buildout this way:
> 
> Is your intention to distribute it for production deployment? Or for  
> development?
> 

For production deployement


Jim Fulton wrote:
> 
>> Then we add "install-from-cache" and "offline" to provide a  
>> installable
>> tarball.
> 
> Have you looked at zc.sourcerelease?
> 

We have quite a similar script that builds a tarball, we created before
you pointed me to zc.sourcerelease. I guess your script handles 
the bootstrap part differently if you didn't need to change it.
So I will try that. But we need to keep our script because it has
more advanced features iirc for our upgrade needs
(like making diffs between two buildouts)


Jim Fulton wrote:
> 
>> Ok, we could release some eggs in some private url to have the proper
>> find-links, but the #egg is quite convenient to avoid this extra step.
> 
> Just to avoid making a distro?  You're already making an tag.
> 
> Why not just use externals?
> 

We are juste tagging. Making a distro is an extra step. Setting up
a bundle is also an extra step.



Jim Fulton wrote:
> 
>> So if we can find a way to automate this..
> 
> I'm still not clear on what "this" is.  Let me see, you want to be  
> able to distribute software that includes develop eggs from svn. Is  
> that right?
> 

No, I want to be able to distribute software that includes eggs from
svn.



Jim Fulton wrote:
> 
>> 2/ the develop problem
>>
>> Another point that would be great to consider: setting up the develop
>> section can be painful when you share a project among many developers,
>> because they need to svn checkout many packages and make sure they
>> have the same folder structure.
> 
> Unless you use externals.
> 

Yup. but that's an extra step, because you need to build a bundle,
then make sure the buildout and the bundle are always synchronized. The
buildout 
was a way to get rid of bundles imho. If I need to work with a bundle, it's
a step back in my opinion.

If we could point an egg in a svn like we do on a file system:

develop =
    /path/in/the/system/my.egg
    svn://path/in/the/svn/my.egg2/trunk
    https://path/in/the/svn/my.egg3/trunk

That would avoid maintaining a bundle


Jim Fulton wrote:
> 
>> 3/ the boostrap.py problem
>> If we want to have a full offline mode (not using your rpm system)
> 
> You mean without zc.sourcerelease?
> 

I guess.. 


Jim Fulton wrote:
> 
>> Oups I forgot one point : being able to tell that a given part in the
>> buildout will be run
>> only under a given platform win32.
> 
> Right, so for other folks benefit, the idea is to be able to say  
> something like:
> 
> [foo platform=win32]
> 
> and have the options defined there provide foo options only on win32.
> 
> I definitely plan to do this.
> 

Great !


++
Tarek
-- 
View this message in context: http://www.nabble.com/setuptools-0.6c7-and-zc.buildout%3A-find-links-egg-fragment-issue-tp15342830p15351725.html
Sent from the Python - distutils-sig mailing list archive at Nabble.com.