Hi Niko,
On 8 Jul 2009, at 15:33, Niko Tyni wrote:
The first patch is just a preconfigured CPANPLUS::Config::System
module
that tells CPANPLUS to install all modules, including core ones, in
the
site directories, even if their Makefile.PL or Build.PL says
otherwise,
so that they will not clobber the ones tracked by our package manager.
Our @INC ordering will make sure that the local version in the site
directory will be the first on the search path.
(We've done this for ages with CPAN.pm and Makefile.PL, and I'm
presently
adding Build.PL support to that as well.)
An alternative solution would be to modify the empty defaults in
CPANPLUS::Config, but this one seems cleaner to me.
No, this The Right Way(tm); ::System was designed for letting vendors/
packagers define defaults that apply to all users on the system.
The other patch is about where the saved CPANPLUS::Config::System
should go. Our policy says that configuration files need to be in /
etc,
and we have /etc/perl first on @INC for things like this.
The patch is something of a hack, I'm not thrilled about messing
inside
the CPANPLUS::Internals namespace. Would you be willing to implement a
cleaner hook for this?
I would, but I'm not coming up with a clean way off the bat; the main
problem
is the Catch22 situation. Everything in CPANPLUS makes conditional
decisions
based on it's configuration settings, but this is not one of them.
I'll give it some thought; in the meantime, the 'hack' is probably
good enough.
If you have any other questions, feel free to ask.
Cheers,
--
Jos Boumans
"Whenever you find you are on the side of the majority,
it is time to pause and reflect." - Mark Twain
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
