2009/4/8 Michael G Schwern <schw...@pobox.com>:
> Gary Holloway wrote:
>> Wouldn't it make sense that if there is a MANIFEST.SKIP file that it
>> would be honored by libscan() so that files that are to be skipped when
>> validating the MANIFEST are also not included in the generated makefile
>> rules (e.g., in the definitions of TO_INST_PM, PM_TO_BLIB) or am I
>> misunderstanding its purpose?
>
> Scenario:  You generate a file but don't want to ship it so you place it into
> MANIFEST.SKIP.  You still want libscan() to see it.

Also you can set up an INSTALL.SKIP which will prevent such files from
being installed, and/or possibly also not copied to the blib dir
(although i admit i forget if the latter is true, but the former
certainly is -- its why i added INSTALL.SKIP to EUI)

Possibly we should respect the INSTALL.SKIP when building the makefile.

Im not a big fan of using hard coded lists for this at all. Such lists
are in my experience highly likely to be OS specific, and leave out
important platforms like Win32 and patterns for non standard editors.

Yves


-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

Reply via email to