perhaps the name kdelibs is up for renewal. How about libkde?Another flaw with the log file idea is that some users install packages with the rpm tool. Unless you patched the Mandrake version of rpm, these wouldn't get appended to the log file.
In my opinion, urpme, when asked to remove a package, should look through
each of it's dependencies, check they're not depended (is that a word?) on
by anything else, and remove only those beginning with lib*. This would
ensure that no other end point packages are removed (for example, you
wouldn't want kdelibs to be removed when uninstalling kdepim)
Of course, it baits the argument AGAINST the over-libification of packages. If an application has runtime libraries associated with it that were written ONLY for that package, and that aren't ever going to be NEEDED by anything else, needing a tool to remove libraries that maybe never should have been lib-ified seems kind of awkward, no?
Still, if the policy is that all library package names must start with lib, that makes the process somewhat easier - but then what about packages like kdelibs?
If everything that uses it has been removed, it should go too.:-)
I agree, not a simple problem.
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
