libtool note in UPDATING

[Kris Kennaway]

On Mon, Feb 27, 2006 at 07:42:03PM -0600, Jeremy Messenger 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.

Probably those all need portrevision bumps since the libraries changed
name.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060227/c45bf21a/attachment.bin