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

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

Thread Previous | Thread Next
Stas Bekman
March 27, 2003 15:06
Re: rfc: a generic solution for dual-life CPAN packages
Message ID:
Andreas J. Koenig wrote:
>>>>>>On Thu, 27 Mar 2003 10:47:35 +1100, Stas Bekman <> said:
>   > Let's say we have a module Foo::Bar, which has a dual life. It's
>   > distributed in the original (master) package Far-Tar-0.01.tar.gz and
>   > is also included in an another package Mar-Car-0.06.tar.gz. The module
>   > Foo::Bar has the same version in both packages. What I'm asking for is
>   > a way to tell the indexer to pick the package Far-Tar-0.01.tar.gz when
>   > asked for module Foo::Bar.
> By hiding the module Foo::Bar in Mar-Car-0.06.tar.gz. If a
> distribution (in this case Mar-Car-0.06.tar.gz) has an inc/ directory,
> all modules below inc/ will be ignored by the PAUSE indexer. By the
> way, the same is true for modules in the t/ directory.

First of all, is that how indexer works today? 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.

See, I haven't known about this indexer feature, if I had I won't have asked 
this question. I suppose that when making a distribution one can always 
organize to put bundled modules into a different directory. After all we are 
using the beloved MakeMaker which lets us do anything we want ;)

But, I'm still thinking about an alternative solution, which doesn't require 
any filesystem layout manipulations. If you don't like the idea of 
introduction of the new variable which will designate the master package, how 
about the following approach.

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.

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

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