[guest - Thu Dec 18 06:25:50 2003]:
Show quoted text> [autrijus@autrijus.org - Tue Dec 16 14:47:20 2003]:
> > It's not a bug it's a feature. How else can your Makefile.PL say
> > use inc::Module::Install
> > when there is no inc/ populated yet?
>
> <me shocked=1 jaw="dropped">
> What the huuh?
>
> Simple, have module authors
> distribute a inc/Module/Install.pm file
You mean, forcing the author into manually doing this:
mkdir inc/
mkdir inc/Module/
cp `perldoc -l Module::Install` inc/Module/
No, this is not going to fly. The author must be able to just say:
use inc::Module::Install;
and have the inc::Module::Install in site_lib to populate everything
inside ./inc/.
Show quoted text> orrr
> don't introduce a new namespace.
> BTW, why did you introduce a new namespace?
Before inc::Module::Install is invented, its predecessor is called
CPAN::MakeMaker. It copies part of itself into ./CPAN/MakeMaker.pm
and bootstrap in similar ways.
The problem is, thanks to how ExtUtils::MakeMaker works, every
distribution name that ends with "::CPAN", like those:
Bundle::CPAN
CPAN
Bot::CPAN
WAIT::Format::CPAN
will inadvertantly also install ./CPAN/MakeMaker.pm as part of
their "make install". That is clearly bad since it corrupts the
copy of CPAN::MakeMaker the user does have.
So, if I simply copy things into ./Module/Install.pm instead of
./inc/Module/Install.pm, then those modules will also run into
the same trouble, if they decide to make use of Module::Install:
Apache::Module
Lib::Module
Test::Without::Module
Tools::Module
So, my assumption is that nobody will upload a module that ends
with "::inc", hence the name "inc" is chosen".
Does this answer your questions?
Thanks,
/Autrijus/
RT for rt.cpan.org