On Fri, Apr 16, 2010 at 9:54 AM, Zefram <zef...@fysh.org> wrote: > That would piss me off. I don't use MANIFEST.SKIP files: I maintain > the MANIFEST manually. If M:B really needs a MANIFEST.SKIP to exist, > for its internal use, then that is a temporary build file and must be > cleaned up no later than "./Build distclean". If it doesn't clean it up, > then it's polluting *my* directory. > > Actually, there's another problem. If it doesn't clean up the generated > MANIFEST.SKIP, then late in "./Build distclean" it notices that this > file isn't listed in MANIFEST and complains. (That is, it isn't listed > if you don't use a MANIFEST.SKIP file, which was the situation requiring > it to be generated in the first place.)
Do you realize that "distclean" is "realclean" plus "distcheck"? > I fail to see why M:B needs a MANIFEST.SKIP when it is not being called > upon to generate a MANIFEST. "distcheck" needs to know what to skip. Some modern ExtUtils::Manifest have a pretty good default. Older ones don't. I'm wondering if the "answer" is to generate MANIFEST.SKIP for the duration of distcheck and related activities *only* and not let it hang around all the way to be cleaned later. That would avoid all the confusion, I think. And if people really need a skeleton MANIFEST.SKIP, we can add "Build manifest_skip" to generate a default one (that then persists) -- David
