>>>>> On Sun, 29 Jan 2006 14:14:30 -0800, Tyler MacDonald <[EMAIL PROTECTED]>
>>>>> said:
> After a bit of poking around in the source of CPAN.pm, the shortest
> bootstrap of a user's home directory that ignores the system-wide CPAN
> config I found was:
> perl -MFile::Path -MCPAN::Config -MCPAN::FirstTime -e '
> $CPAN::Config = {}; mkpath("$ENV{HOME}/.cpan/CPAN");
> CPAN::FirstTime::init("$ENV{HOME}/.cpan/CPAN/MyConfig.pm",
> autoconfig => "yes")
> '
My current version of the FAQ section of the manpage has the following:
=item 5)
I am not root, how can I install a module in a personal directory?
First of all, you will want to use your own configuration, not the one
that your root user installed. The following command sequence is a
possible approach:
% mkdir -p $HOME/.cpan/CPAN
% echo '1;' > $HOME/.cpan/CPAN/MyConfig.pm
% cpan
[...answer all questions...]
> I've attached a patch that makes it so that CPAN.pm has a new function,
> "userconfig", and when the current user does not have permission to create
> their lockfile, *and* they don't have a MyConfig.pm yet, they are given the
> opportunity to create their own CPAN config, using all of the system-wide
> defaults *except* paths where CPAN does it's work. Let me know what you
> think.
It looks cool and straight forward. I wonder if you would still
recommend your own patch now that I have shown you the section 5 of
the FAQ?
If yes, I think I'd call it "mkmyconfig".
And when you could please add a paragraph of documentation, it's in in
a second.
Thanks,
--
andreas
