-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote: > Hey, > > On 9/27/07, Jim Fulton <[EMAIL PROTECTED]> wrote: >> On Sep 26, 2007, at 8:26 PM, Tres Seaver wrote: > [snip] >>>> Including a file other >>>> that README in the root requires extra effort that I don't want to >>>> require -- writing setup.py files is hard enough as it is. >>> Put the "real" README.txt and CHANGES.txt in the actual package: the >>> version which is a peer of 'setup.py' should be a stub which points to >>> the "real" versions. >> I can live with this, but I don't like it. It feels more complicated >> to me. > > I don't like it either. I thought we resolved this though so I'm not > sure why we're discussing this. CHANGES.txt in the root dir it is, > right?
- -1. I argued for putting the CHANGES.txt and the "real" README.txt in the *package* dir, making them available in the *installed egg*, not just the source ditribution. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG++AV+gerLs4ltQ4RAv11AJ48x6iioc9AWavIZS5zvQvpR/X1dwCgsuro 3CvFwTcmCfYqXFpICxDGCxk= =+T+6 -----END PGP SIGNATURE----- _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com