[Distutils] Building an egg from Subversion using zc.buildout

[Jim Fulton]

On Jan 29, 2007, at 4:52 PM, Martin Aspeli wrote:

> Jim Fulton wrote:
>
>> So do you get a develop egg and egg link or a regular egg for each of
>> these packages?  If the later, as I fear, I think you have a problem.
>
> I think the latter (I *just* deleted my test instance and I don't want
> to do it all again now), but why is it a problem?

So, from your example, you now have a kss.core-0.1dev egg.   It isn't  
a real release. It reflects the state of your subversion repository  
at the time you happened to run the buildout.

My guess is that if you run the buildout again, the egg won't be  
recreated.  You won't be tracking subversion changes as you wished.

Further, if you use a shared eggs directory, any other buildouts will  
likely use that same egg, which has a more or less random snapshot of  
the software.  I suggest that this is a bad thing.

IMO, this is what you really want:

- You want something to check out your project and make it a develop  
egg.

- When you run buildout later, you want something to do an svn up in  
the checkout and to rerun setup (in case there are extensions).

I think this "something" should probably be a recipe (or a feature of  
some existing recipe).

I wonder what easy_install does in a case like this.  For example, I  
wonder if easy_install would download and rebuild the egg every time  
you ran it.   Of course, with easy_install, you probably would only  
run it once, but, again, then you wouldn't be tracking subversion.

Jim

--
Jim Fulton			mailto:jim at zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org