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

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

Thread Previous | Thread Next
Autrijus Tang
March 27, 2003 19:20
Re: rfc: a generic solution for dual-life CPAN packages
Message ID:
On Fri, Mar 28, 2003 at 10:04:50AM +1100, Stas Bekman wrote:
> First of all, is that how indexer works today?

Apparently yes.

> Is that documented as a public "interface", so it won't change in the
> future?
> Second, as Autrijus followed up, it seems that it's not going to be inc.

I love the name 'inc', but I am open to other reasonable suggestions
before PAUSE deem it a public interface.  But whatever the final name is,
it is imho useful (and not really klugy) to have the indexer ignore
specific directories like t/ (and possibly inc/), without needing to
specify it manually via BUNDLED.

> We introduce a new file called BUNDLED (similar to MANIFEST), which will 
> list all the packages that are bundled and are to be ignored by the 
> indexer. This solution is simple, and gives a full control to developers, 
> if at some point in the future they decide to split one of the modules into 
> a separate package, while keeping it bundled with the previous hosting 
> package, all they need to do is to add this module name (actually file 
> path) to the file BUNDLED, and release it on CPAN.

This sounds like a Very Good idea so users of Module::Install can choose
to use whatever prefix they want, instead the inc:: prefix.

So... should BUNDLED use the MANIFEST.SKIP syntax (i.e. "^inc/") or the
MANIFEST syntax (list files explicitly)?  I'd think that the regex
approach is easier to use, with no obvious drawbacks.


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