develooper Front page | perl.perl5.porters | Postings from March 2003

Re: rfc: a generic solution for dual-life CPAN packages

Thread Previous
Autrijus Tang
March 28, 2003 00:30
Re: rfc: a generic solution for dual-life CPAN packages
Message ID:
On Fri, Mar 28, 2003 at 01:24:37PM +1100, Stas Bekman wrote:
> Why this is beneficial to the /inc solution:
> - it's flexible and not hardcoded, casted in stone, solution

This I agree.  However I'd argue for a default INDEX (in case
that the distribution does not come with one) that includes at
least "t/", much like the current default for MANIFEST.SKIP.

Without this, people relying on the indexer not indexing t/
modules may be unpleasantly surprised.

> - currently used hadrcoded solution using /inc is still supported, by
>   simply adding /inc to /INDEX (-/inc)

Sure, I can live with that, although I'd still like it to be
in the default. :-)

> - CPAN::MakeMaker only needs to include the bundled files in /INDEX
>   and may put them under any dir it feels like.

s/CPAN::MakeMaker/Module::Install/ mentally...

> I don't really care how this special file is to be called, or what the
> inclusion/exclusion syntax is. the point is to have the functionality
> in place.

Same sentiment here.

Although -- is there a common use case for the '+' part of your proposed
INDEX spec?  IMHO, a MANIFEST.NOIDX file that has the same regex-driven
syntax as MANIFEST.SKIP will quite suffice:

    ^lib/private\b  # exclude lib/private/ and lib/

This has the benefit of reusing the ExtUtils::Manifest parsing routines,
and makes it easier for both carbon- and silicon-based entities.


Thread Previous Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About