On Thu, 26 Aug 2010 22:44:53 -0400 Richard Freeman <[email protected]> wrote: > The problem is that lots of stuff is installed which depended on > either of those packages, and paludis captured at the time of > installation that lzma-utils was used to satisfy the dependency, and > it keeps coming up. Re-installing anything that had a direct > dependency on lzma-utils will tend to fix the problem (they now > depend on xz-utils), but is a real pain. > > How can I fix these kinds of issues without rebuilding everything. > This isn't a library linking issue - those packages will work just > fine as long as they can access the binary (assuming they even need > it runtime).
The way Paludis does it is the correct way. For example, if an installed package is linked against a particular library, and the ebuild is then updated to use || ( somenewlib thelibyouhave ), you wouldn't want your package mangler to think that it could remove thelibyouhave. Another example was when a package's pkg_*rm functions are changed not to use a particular tool any more. The run dependency remains in the installed ebuild, but is removed from the ebuild in the tree. You wouldn't want your package mangler to remove that tool, though, because then the uninstall of that package would fail later on. This isn't something we can safely change, and as a user it's not something you can fix without intimate knowledge of every package in question. Just because the first 99 packages you check that use lzma-utils can be switched to xz-utils without a rebuild does not mean that the 100th can. If you're *really* sure you're right, you can sed VDB. But that's something you should only do with extreme caution... -- Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
