I've actually never heard of '#!include_default'. It's supported by EU::Manifest?
I agree that if it's well-supported in the wild, it would probably be preferable to use it. -Ken On Fri, Jan 2, 2009 at 2:49 PM, Johan Vromans <jvrom...@squirrel.nl> wrote: > Hi, > > Often I want to add a couple of excludes to the MANIFEST generation. > > Creating a MANIFEST.SKIP with the excludes is a start, but then I > loose the 'standard' set of excludes. > > Adding '#!include_default' cures this, but "./Build manifest" inserts > the complete list of standard excludes. Should this list change in the > future then my MANIFEST.SKIP does not profit from these changes. > > Wouldn't it be better to make #!include_default an instruction that > does not get expanded in the MANIFEST.SKIP? So I can write a neat and > concise MANIFEST.SKIP like: > > #!include_default > Released/* > > and have it stay neat and concise? > > To get the contents of the standard set of excludes, e.g., when I want > to remove some excludes, a Build command like > > ./Build manifest.skip > > would be useful to create a MANIFEST.SKIP with the #!include_default > expanded. > > Just some 2009 ideas... > > -- Johan > http://johan.vromans.org/seasons_greetings.html > > > >
