Massive portupgrade without being interrupted by configuration
screens?
Jerry
freebsd.user at seibercom.net
Sun Oct 3 11:09:26 UTC 2010
On Sun, 03 Oct 2010 09:59:19 +0000
Thomas Mueller <mueller6727 at bellsouth.net> articulated:
> >From "Elias Chrysocheris" <eliaschr at cha.forthnet.gr>:
>
> > 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: skv at FreeBSD.org
>
> 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?).
If you were to use 'portmanager' with its '-p' option, it would rebuild
all ports that depend on the new version of Perl as well as any ports
that depended on those ports as well. It would insure that the
dependency links were fully updated. There is then no need to run the
superfluous "perl-after-upgrade' script; although, you are free to do
so if you so desire.
--
Jerry ✌
FreeBSD.user at seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
Hartley's First Law:
You can lead a horse to water, but if you can
get him to float on his back, you've got something.
More information about the freebsd-questions
mailing list