Re: install/45335: postinstall: obsolete libs: use distribution sets

["Martin S. Weber" <Ephaeton%gmx.net@localhost>]

The following reply was made to PR install/45335; it has been noted by GNATS.

From: "Martin S. Weber" <Ephaeton%gmx.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: install/45335: postinstall: obsolete libs: use distribution sets
Date: Thu, 1 Mar 2012 09:47:01 -0500

 On Thu, Mar 01, 2012 at 10:11:46AM +0100, Martin Husemann wrote:
 > On Thu, Mar 01, 2012 at 01:30:05AM +0000, Martin S. Weber wrote:
 > >  IMO, for NetBSD controlled directories (i.e. /lib, /usr/lib) deleting 
 > >  everything which isn't in the distribution's mtrees should be fine, 
 > > shouldn't
 > >  it?
 > 
 > You need to leave around, for each shared library, for each major
 > present the lib with the highest minor.
 
 See the example I gave in the original PR. I hosed my release system
 by trying out a feature in -current to aid in PR solving. Then I went
 back to release as -current was unstable for me at the time, had
 postinstall run and deleted the wrong libraries. Why? Because for
 each shared library, for each major present, the lib with the highest
 minor was kept. NOT the one that was needed in the distribution due
 to the own distribution mtrees. Actually we do have the mtree files
 according to the sets; why would you try and guess to know better?
 The REAL dependencies are recorded already, so let's use them.
 
 
 > 
 > Old static libs can just go away, IMHO.
 
 Yes, if "old" = "no longer needed for the version that just was
 installed", not if "old" = "the one with the lower version number".
 See original PR and above for the kind of breakage that ensues if
 you opt for the latter.
 
 > 
 > You are only talking about updates via sysinst from official (i.e. well
 > tested) distribution media, I suppose? You certainly do not want to do
 > this kind of cleanup on -current when updating from source.
 
 Sure, why not?
 
 -Martin