Michael G Schwern wrote: >The third order solution is for MB to recognize that the MANIFEST.SKIP >has been altered and leave it alone.
Sounds good to me. >Alternatively, just don't delete it. 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.) I fail to see why M:B needs a MANIFEST.SKIP when it is not being called upon to generate a MANIFEST. -zefram
