On Thu, 29 Mar 2007 10:36:34 -0500 (CDT)
"Jeremy C. Reed" <reed@reedmedia.net> wrote:

> On Thu, 29 Mar 2007, Przemys_~Baw Pawe_~Bczyk wrote:
> 
> > I installed from scratch NetBSD 4.99.16 yesterday. Then I installed
> > my basic set of applications from packages-2006Q4.
> > 
> > 1) X Window System
> > a) shared object libz.so.0 not found
> > b) shared object libstdc++.so.5 not found
> > 
> > I had to:
> > a) ln /lib/libz.so.1.0 -> /usr/lib/libz.so.0
> > b) ln /lib/libstdc++.so.6.0 -> /lib/libstdc++.so.5
> > 
> > 2) Sylpheed
> > a) libssl.so.3 not found
> > b) libcrypto.so.2 not found
> > 
> > I had to make appropriate symlinks:
> > a) ln /usr/lib/libssl.so.4 -> /usr/lib/libssl.so.3
> > b) ln /lib/libcrypto.so.3.1 -> /usr/lib/libcrypto.so.2
> 
> Thanks for the note. This may help others. Nevertheless, there may be 
> incompatibilities.
> 
> NetBSD doesn't provide pre-built packages against
> "development" (-current) branch of NetBSD. If there is a huge enough
> interest of having NetBSD provide pre-built packages for -current
> NetBSD, let us know.
> 
> The recommended way to install packages on a -current system is to
> build your packages from source using "pkgsrc".
> 
I think there's a deeper issue here.  Suppose that he'd started with
3.1, installed those packages, then upgraded to (say) 5.0.  Presumably,
the "delete obsolete files" part of the upgrade would remove
libssl.so.3, etc., at which point his packages no longer work.  That
seems to be a serious break in backwards compatibility.  (Or am I
missing something?)


		--Steve Bellovin, http://www.cs.columbia.edu/~smb