-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> On 9/27/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
>> On Sep 26, 2007, at 8:26 PM, Tres Seaver wrote:
>>>> 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,
- -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 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
-----END PGP SIGNATURE-----
Zope3-dev mailing list