* Jeffrey Thalhammer <[EMAIL PROTECTED]> [2008-08-20T12:42:49] > But there is some debate about whether the MANIFEST and other > metafiles should be put in the source code repository. My gut feeling > is that MANIFEST is a generated file, therefore it does not go in the > repository. Instead, the MANIFEST.SKIP file should be carefully > crafted to ensure that the MANIFEST is correct. However, this raises > a question: How do you ensure that *unexpected* cruft files don't end > up in the MANIFEST?
I don't store MANIFEST, I store MANIFEST.SKIP. In fact, on my latest dists, I only include the MANIFEST as a couresty to stupid software that expects it. I don't see any value in having a MANIFEST file in the dist, let alone in my repo. I have other tools for managing what ends up in the tarball; I configure those instead of MANIFEST, which I find to be a fairly anemic tool. -- rjbs
