libtool note in UPDATING

[Chris]

On 28/02/06, Jeremy Messenger <mezz7 at cox.net> wrote:
>
> On Mon, 27 Feb 2006 16:53:57 -0600, Kris Kennaway <kris at obsecurity.org>
> wrote:
>
> > On Mon, Feb 27, 2006 at 02:06:55PM -0800, Christopher Kelley wrote:
> >> Am I reading the entry for libtool in UPDATING correctly?  It seems to
> >> me to basically say "There's no way to tell you how to successfully
> >> update your ports with the new libtool, hope you really understand how
> >> all the ports interact with each other, good night and good luck."
> >>
> >> Now, I *DO* sort of understand the need for this change from reading
> the
> >> entry, and I'm not arguing the fact that the change needed to be made.
> I
> >> just don't know where to go from here because now I'm afraid to update
> >> any of my ports since I'm not sure I would understand the output of the
> >> -n flag enough to figure out how to update my ports.
> >>
> >> Is there a more straightforward explanation of how to upgrade ports
> with
> >> the new libtool?
> >
> > Basically, portupgrade -a should be OK (but watch out for the perl
> > upgrade as well, i.e. read that entry too).  If you run into problems
> > let us know; I'd like to refine that entry with a working prescription
> > before the release.
>
> I doubt the 'portupgrade -a' will working on any ports that depend on
> glib12, gtk12 and etc. I would go with -af or -afr to force rebuild all
> apps if you want to use portupgrade instead remove ports and reinstall
> stuff as suggested in the UPDATING.
>
> Cheers,
> Mezz
>
> > Kris
>
>
> --
> mezz7 at cox.net  -  mezz at FreeBSD.org
> FreeBSD GNOME Team
> http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org
> _______________________________________________



I am guilty of not reading UPDATING on this but I used -a and -i on first
few machines and have so far not seen any problems as a result.

Chris