-----BEGIN PGP SIGNED MESSAGE-----
Philipp von Weitershausen wrote:
> Jim Fulton wrote:
>> On Sep 26, 2007, at 1:18 PM, Fred Drake wrote:
>>> On 9/26/07, Martijn Faassen <[EMAIL PROTECTED]> wrote:
>>>> What does one need to tell setup.py to make sure CHANGES.txt is
>>>> available? I understand it isn't by default, then? Hm, it does appear to
>>>> be there by default. I checked grok 0.10's tgz and it's there, and we
>>>> didn't do anything special.
>>> Do you mean available in the unpacked sdist, or as part of the
>>> installation? I don't think any of README, README.txt, CHANGES,
>>> CHANGES.txt (from the root of the distribution, not from inside the
>>> package) are actually installed. If they are, I'd love to know where.
>> By default READM(.txt) is installed in a source distribution. Anything
>> else in the root (aside from setup.py of course and source files
>> themselves) aren't without extra setup chants. (These chants can be
>> figured out with some effort. I never remember them, so, if I want to
>> do something like this, I have to figure them out again or try to find
>> an example with them.)
> Actually, no package data is ever included unless you're either
> * working from an svn checkout, in which case setuptools will use the
> list of which files are in svn and which aren't as a hint of what to
> include and what not
> * creating a MANIFEST.in file to tell setuptools what to include explicitly.
or you write your own package finder. Frankly, anybody who is making
package releases from anything other than a versino-controlled checkout
Further, anybody who finds the effort of creating a "fresh' checkout
bevore making a release too burdensome should consider themselves
self-selected out of the "release manager" pool.
I'm *not* kidding about that: taking shortcuts durng the release
process transfers pain / cost to everyone downstream.
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