On Wed, Sep 28, 2005 at 12:26:15PM -0500, Ken Williams wrote:
> >Hmmm. Throw in a way to include the default MANIFEST.SKIP and you'll
> >have yourself a winner.
>
> If "the"default M.S changes, though, I wouldn't want to auto-update.
> Too much potential for "hey, where did my files go?".
That's up to the user to decide. #include_default or something.
Anyhow, a much larger problem than the potential for a new default
MANIFEST.SKIP to screw up your distribution (something I've never had a report
of from the wild) is the problem of not seeing new updates to MANIFEST.SKIP.
Especially having to do with new MakeMaker and Module::Build internal things.
A "copy the default into my own MANIFEST.SKIP" encourages this problem.
I've had several requests over the years for this feature. That I can
recall, I've never had anyone complain that a new default MANIFEST.SKIP
suddenly started removing files from their distribution. If this *really* is
a problem it might make sense to include a way to override previous skips.
A way to say "always include those matching these files no matter what the
earlier rules say". But this feels rather YAGNI.
--
Michael G Schwern schwern@xxxxxxxxx http://www.pobox.com/~schwern
On error resume stupid
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|