perl-after-upgrade mistakenly thinks nothing needs to be done

2013-04-11 Thread Mike Brown
Hi all, I'm running 8.3-RELEASE and thought I'd update Perl from 5.12 to 5.16. Silly me. I updated my ports snapshot, and as per UPDATING, ran portmaster -o lang/perl5.16 lang/perl5.12 This went OK, so I then ran perl-after-upgrade, with and without -f. It scans the packages and finds

Re: perl-after-upgrade mistakenly thinks nothing needs to be done

2013-04-11 Thread Mike Brown
Thanks for the replies; I really appreciate it. Alexandre wrote: Have you followed steps described in perl-after-upgrade man page? $ man perl-after-upgrade Yes, except for the last step (deleting old CONTENTS backups), since the previous steps didn't seem to do what they should. As I said

Re: perl-after-upgrade

2005-07-07 Thread legalois
Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl

Re: perl-after-upgrade

2005-07-07 Thread Bob Hall
On Thu, Jul 07, 2005 at 06:55:58PM +0200, legalois wrote: Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get

Re: perl-after-upgrade

2005-07-07 Thread Paul Schmehl
--On Thursday, July 07, 2005 14:39:44 -0400 Bob Hall [EMAIL PROTECTED] wrote: As I stated above, I used portupgrade. That means that any messages at the end of the perl upgrade scrolled off the screen and out of the screen buffer when portupgrade carried out the next install. One of the

Re: perl-after-upgrade

2005-07-07 Thread RW
On Wednesday 06 July 2005 20:10, Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book

Re: perl-after-upgrade

2005-07-07 Thread Bob Hall
On Thu, Jul 07, 2005 at 01:53:48PM -0500, Paul Schmehl wrote: --On Thursday, July 07, 2005 14:39:44 -0400 Bob Hall [EMAIL PROTECTED] wrote: As I stated above, I used portupgrade. That means that any messages at the end of the perl upgrade scrolled off the screen and out of the screen

perl-after-upgrade

2005-07-06 Thread Bob Hall
I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I've got a book that said to use # perl perl-after-upgrade

Re: perl-after-upgrade

2005-07-06 Thread Bob Hall
On Wed, Jul 06, 2005 at 03:10:04PM -0400, Bob Hall wrote: I don't know squat about perl. I recently ran portupgrade, which upgraded perl. Goose stopped working, because the location for Curses.pm was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't get it to run. I found

Re: Can't get perl-after-upgrade to run

2005-06-26 Thread Dick Hoogendijk
On 26 Jun Dominique Goncalves wrote: And, if I type sh perl-after-upgrade -f I get the EXACT same output as above, leading me to believe it is ignoring the -f option. Use /usr/local/bin/perl-after-upgrade To OP: are you sure you did a rehash ? The file not found seems to tell you, you

Should I Keep Default Perl After Upgrade to 5.8 on FBSD 4.9?

2004-03-24 Thread Drew Tomlinson
I upgraded my 4.9-RELEASE system to use Perl 5.8.2 from ports. Is there any reason to keep the default 5.005.03 version? If not, are there any steps required beyond deleting /usr/local/lib/perl5/5.00503? Thanks, Drew ___ [EMAIL PROTECTED] mailing