At 17:03 +0100 8/24/06, David Cantrell wrote:
>Run the CPAN shell as root as all will be well.
Idonwannadodat!
Although I have root privileges on all machines around here there are still two
of use who install things and I much prefer NOT to step on the War Department's
toes. She's the one who
At 11:32 am -0600 24/8/06, Doug McNutt wrote:
At 17:03 +0100 8/24/06, David Cantrell wrote:
Run the CPAN shell as root as all will be well.
Idonwannadodat!
...The result is that I can compile and install without being root.
My stuff does not get any chance to screw up something like a syste
On Thu, August 24, 2006 2:39 pm, John Delacour said:
> I have never run the CPAN shell as root and I don't see what problems
> you're referring to. I just do 'sudo cpan' and everything is
> installed where it should go.
>
> Eremita:~ jd$ sudo cpan
That's running it as root, via sudo.
I don't th
At 19:39 +0100 8/24/06, John Delacour wrote:
>All tests successful, 1 subtest skipped.
>Files=18, Tests=503, 3 wallclock secs ( 1.75 cusr + 0.50 csys = 2.25 CPU)
> /usr/bin/make test -- OK
>Running make install
>Installing /usr/local/lib/perl5/5.8.8/CGI.pm
>Installing /usr/local/lib/perl5/5.8.8
I have never run the CPAN shell as root
I beg to disagree ...
and I don't see what problems you're referring to. I just do 'sudo
cpan'
unless, of course, you actually do it as something like
sudo -u myuser cpan
On Aug 24, 2006, at 5:04 PM, Doug McNutt wrote:
I guess I wasn't clear. I want the modules installed in my $HOME
directory so that they won't
1) Get lost when a newer OS gets installed - especially with Linux.
2) Get in the way of someone else's, the main geek - my wife's,
idea of what shou
