-----BEGIN PGP SIGNED MESSAGE-----
Marius Mauch wrote:
| The purpose of this is to keep the system operational after library
| upgrades until all affected packages could be rebuilt and to simplify
| the process, not to avoid the rebuilds.
I couldn't find it mentioned in your email, but if portage is
effectively doing reference counts, what happens when its reference
count gets to 0? Once no ebuilds rely on the old library is it removed
automatically, or do the "you need to rebuild these" message just go away?
Is there a way to have portage delete the libraries once it's sure
they're no longer necessary? If so, is that done by rebuilding the
owning package itself, or by editing the owning pacakge's contents and
removing the old library?
Does @preserved-rebuild contain just the affected packages, or the
package containing the old library as well? (i.e. Does an "emerge
@preserved-rebuild" ensure that the old library will no longer exist on
your system, or not?)
Basically, if I can safely replace "revdep-rebuild" with "emerge
@preserved-rebuild" then I'd be happy to keep it enabled. If it's going
to leave cruft on the system (or then require manual rebuilds of
packages containing preserved libraries to clear out the cruft) then I'd
personally be inclined to turn it off and stick with revdep-rebuild...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
-----END PGP SIGNATURE-----
email@example.com mailing list