in reply to Re: perlbrew and cpan
in thread perlbrew and cpan

Thx.

So it looks like I may have messed up my cpan and my system perl. And there is no good way to fix it except to restore from backup?

lc

Replies are listed 'Best First'.
Re^3: perlbrew and cpan
by ikegami (Patriarch) on Aug 07, 2014 at 16:43 UTC

    You can fix the file ownership as follows:

    sudo chown -R $USER "${PERLBREW_ROOT:-$HOME/perl5/perlbrew}"

    The following fixes the group too, assuming the group name should be the same as your user name:

    sudo chown -R $USER:$USER "${PERLBREW_ROOT:-$HOME/perl5/perlbrew}"

    You didn't say how you messed up your system perl, so I can't offer any advice on how to fix it.

Re^3: perlbrew and cpan
by Anonymous Monk on Aug 07, 2014 at 08:44 UTC

    So it looks like I may have messed up my cpan and my system perl. And there is no good way to fix it except to restore from backup?

    Why does it look that way to you?

      I find it strange that perlbrew allows the system perl to be updated; regardless that it's been ran with a sudo.

      Shouldn't that happen only after perlbrew off had been given? when the system perl is available.

        I find it strange that perlbrew allows the system perl to be updated

        The biggest reason to use perlbrew is to avoid breaking tools that use the system Perl. (Most people will phrase that as "I can't get permission to modify the system Perl".) Disappearing the system Perl would not be a good thing.

        perlbrew is a specialized PATH manipulator, that's it.

        I find it strange that perlbrew allows the system perl to be updated; regardless that it's been ran with a sudo.

        Shouldn't that happen only after perlbrew off had been given? when the system perl is available.

        Um, what are you talking about? Where is your proof (shell session log)?