On Mon, Jan 05, 2009 at 03:02:24PM -0500, Barry Warsaw wrote: > I just converted Mailman 3 to use zc.buildout. Thanks to Gary Poster > for providing some good examples and the impetus for my force vacation > hacking. :) > > I especially like being able to specify defaults in my ~/.buildout/ > default.cfg file. One thing that bugs me though is that I can't use > environment variables like $HOME there.
Seconded: https://bugs.launchpad.net/zc.buildout/+bug/190260 > This is a minor pain because > I can't share my .buildout directory between Linux and OS X machines > (say, via version control). It appears as though I have to be > explicit in the path, with /Users/barry on OS X and /home/barry on > Linux. > > Similarly, in my buildout.cfg file, if I include a develop field > pointing to some source directories (other than .), I can't use $HOME/ > projects/foo/bar here. > > Any thoughts on supporting environment variables in .cfg files? Or do > they work and I'm just experiencing operator error? ;) AFAIK, no. > I'm also wondering, does it make sense to put develop-eggs and parts > in say ~/.buildout? No, since those are specific to a particular project and shouldn't be shared. (Actually, I don't understand what 'develop-eggs' is for, other than that removing it tends to fix weird problems after switching from a develop-egg to a normal egg.) > I kind of dislike having artifacts like these > live in my version controlled source directory (well, there's bin too, > but I can kind of live with that). What's the best way of doing that? echo 'bin parts develop-eggs' > .csvignore svn propedit svn:ignore . bzr ignore bin parts develop-eggs or the equivalent for the VCS of your choice. HTH, Marius Gedminas -- If something has not yet gone wrong then it would ultimately have been beneficial for it to go wrong.
signature.asc
Description: Digital signature
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
