>From "Elias Chrysocheris" <[email protected]>: > If you are sure that the default configuration settings are OK for you, then > one way is to perform a portupgrade with the switches --batch --yes, like > portupgrade --batch --yes -a
> This will assume that the default settings are those you like and will not ask > you anything about configuration screens e.t.c. > Elias Idea is that I might want to configure some of the options, so I can't use --batch=YES unless I configure all options beforehand, meaning I have to find what ports are to be upgraded and which of those have user-selectable options. Are there any adverse side effects if I use portupgrade some of the time, and postmaster other times? Reason for wanting to do all "make config"s beforehand is not only efficiency and ability to run unattended, but the ability to recover from a typo at the config dialog interface, which can be confusing, on when to press spacebar, tab, enter, up- and down-arrows. Now I see in UPDATING file, date 20100915, that lang/perl5.12 has been updated to 5.12.2. 20100915: AFFECTS: users of lang/perl5.12 AUTHOR: [email protected] lang/perl5.12 has been updated to 5.12.2. You should update everything that depends on perl. The easiest way to do that is to use "perl-after-upgrade" script supplied with lang/perl5.12. Please see its manual page for details. If you want to switch to lang/perl5.12 from lang/perl5.{8,10} please follow instructions in the entry 20100715 in this file. I only saw this via FreeBSD web site Oct 3 (20101003), after my original inquiry. Does this mean I have to go through all the troubles again? I already successfully portupgraded Perl to 5.12.2. But I guess I need to read "perl-after-upgrade" script before doing anything (including panicking?). Tom _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
