Author mpm
Recipients meatballhat, mpm, ronaldoussoren, tarek
Date 2010-08-01.19:21:38
SpamBayes Score 2.73155e-05
Marked as misclassified No
Message-id <1280690501.61.0.0194844497224.issue8688@psf.upfronthosting.co.za>
In-reply-to
Content
This change just wrecked Mercurial's release build process.

We've been building Mercurial release tarballs with a Makefile target wrapped around sdist for most of five years, and we've never had or wanted a MANIFEST.in file. We generate an exact, complete, and correct MANIFEST ourselves with:

 hg manifest > MANIFEST

This fix ignores that MANIFEST entirely and attempts to build a new one even though MANIFEST.in doesn't exist.

So not only does this change years of documented behavior in a way that very nearly caused us to ship a tarball missing over a thousand files, it means doing what we want to do with sdist (ship precisely the files listed in our version control manifest) is now significantly harder.

Unfortunately, this fix is now in a long-lived Python release which we support, which means we're stuck with it.
History
Date User Action Args
2010-08-01 19:21:41mpmsetrecipients: + mpm, ronaldoussoren, tarek, meatballhat
2010-08-01 19:21:41mpmsetmessageid: <1280690501.61.0.0194844497224.issue8688@psf.upfronthosting.co.za>
2010-08-01 19:21:40mpmlinkissue8688 messages
2010-08-01 19:21:38mpmcreate