-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry I'm a bit late to the thread,
Just to add that empathy preserves libemapthy in this manner too. On 05/07/10 17:40, Gilles Dartiguelongue wrote: > > 1. How is it different than preserved-libs feature from > portage-2.2 ? The issue that I have with you argument is that > you encourage breaking user apps at build time instead of > leaving the user some time to run revdep-rebuild or any other > tool needed when user wishes so. This is different from preserve-libs because FEATURES="-preserve-libs" doesn't stop these calls from keeping old libraries around. Also, once preserve-libs has been used, a normal revdev-rebuild won't spot these issues, and cruft-checkers can't find them because they're classed as part of the new package. I understand we have users who want this feature, and also that we advise everybody to read through every single elog message ever made. Having said that, I personally know how to run revdep-rebuild, and I do it often so that when I'm upgrading 100+ packages in one go, I don't then have to sit around reading through every elog message to make sure that a library I didn't ask for doesn't accidentally get left on my system for all time. I can live with this for in places where it causes massive breakage (openssl/libpng/libjpg), because it's genuinely useful, but I think it should be restricted to such important packages, or at least disabled by FEATURES="-preserve-libs". Ideally, these calls should either adhere to FEATURES="-preserve-libs", or there should be a tool that can identify which files portage has preserved, and allow easy rebuilding of dependent packages, and removal. At the moment, I'm having to manually grep ebuilds, ls the libraries and run revdep-rebuild over them one at a time... Mike 5:) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEARECAAYFAkw+y6oACgkQu7rWomwgFXoehQCgsrbUBRorY6J4rBmASh16t1eP YzoAnAhAi7kWd/bI9xhUh8UHMFfCR5xY =OOj9 -----END PGP SIGNATURE-----
