Subject: Re: Updating packages in going from NetBSD 1.5 -> 2.0
To: None <firstname.lastname@example.org>
From: Steven M. Bellovin <email@example.com>
Date: 12/11/2004 13:57:48
In message <41BB3098.firstname.lastname@example.org>, Scott Presnell writes:
> I'm in the midst of upgrading my i386 system
>from NetBSD 1.5 to 2.0. At the system level things
>seem to be going well.
>WRT packages, I had been hacking buildlink files to
>keep packages from being "needlessly" updated.
>Now I'm trying to make a fresh start. I have some questions:
>1) native pthread: should I take this opportunity to remove
>any pthread packages and rebuild packages with the system/native
>/usr/lib/libpthread? Or is there still a role for the package
>2) how do /usr/lib/libintl and the gettext-lib package work
>together? Often I get link results such as:
>/usr/bin/ld: warning: libz.so.0, needed by /usr/pkg/lib/libgnomeui.so,
>may conflict with libz.so.1
>/usr/bin/ld: warning: libintl.so.0, needed by
>/usr/pkg/lib/libgnomeui.so, may conflict with libintl.so.2
>(same question for zlib I guess)
>Is this the expected result, or is there a better solution?
>3) I'm trying to use /usr/pkgsrc "-current" I guess, rather than
>one of the quarterly freezes. Is there a branch of the package
>system I should try to use in outfitting a newly updated 2.0 system?
I decided that the easiest thing was to recompile everything, using
pkg_conf to build the list of stuff to rebuild. You could figure out
minimal rebuilds via pkgdepgraph, but I suspect you'll run into
problems with other things being out of date.
--Steve Bellovin, http://www.research.att.com/~smb