On Mon, May 15, 2006 at 02:17:53PM -0400, Tres Seaver wrote: | -----BEGIN PGP SIGNED MESSAGE----- | Hash: SHA1 | | Sidnei da Silva wrote: | > Also on a similar subject, running 'make install' from a checkout only | > copies packages that have a 'SETUP.cfg' inside. Is that intentional? | > | > I thought someone was in charge of fixing the 'make install' dance. | | What packages are you expecting to see installed which are not? I think | the intent was to quit installing by default the "extras" which are | part of the checkout, but never part of a release. Erm, 'App' and 'Zope2' to boot? :) -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

On Mon, May 15, 2006 at 03:25:55PM -0400, Fred Drake wrote: | On 5/15/06, Sidnei da Silva <sidnei@enfoldsystems.com> wrote: | >Also on a similar subject, running 'make install' from a checkout only | >copies packages that have a 'SETUP.cfg' inside. Is that intentional? | > | >I thought someone was in charge of fixing the 'make install' dance. | | Someone might be, and it might even be me (I don't recall). There's | been no time for me to work on that, and I don't foresee any in the | near future. | | You're welcome to look into this yourself. I've not been convinced | that this is actually an important use case. The whole thing seems a bit backwards to me. I'm not sure why some parts of the Zope2 tarball-making process do a checkout from a SVN tag. Why not check everything out of SVN then? I would have thought the procedure for building a tarball would be: 1. Checkout SVN tag 2. Build tarball from the tag checkout (no network required in this step) In the current process it is possible to checkout trunk and make a tarball that has parts of trunk and parts of a tag. One way or another, the real thing I'm after is to be able to run 'make install' from a checkout and end up with the same as running 'make install' from a tarball. If that requires building a tarball and then extracting the tarball it's fine with me, as long as the makefile takes care of it. Heck, once you have all the parts needed to build the tarball, you would be set, no need to tar and then untar. So, I think the real question is: - Can we make it so running 'make zpkg' or 'make pre_sdist' or something builds a directory that is ready to just be tar'd up to generate the final tarball, and that doing 'make install' will pick depend on this step and then run 'install.py' from that directory? I don't think that's too hard. I've played a bit with it, and found out 'zpkgtools' needs to be added to the 'buildsupport' dir at least, if you don't want to require zpkg to be installed, and then I ran out of time after generating a tarball. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214