Michał Górny wrote: > Consider the following: > > 1. A depends on B, both are installed, > > 2. dependency on B is removed, emerge --depclean uninstalls B thanks > to dynamic-deps, > > 3. B is treecleaned (nothing depends on it),
So far I follow. > 4. old version of A is removed (user doesn't update it yet), ebuild removed from tree. > therefore dependency on B is restored from vdb. Why would removing the ebuild from the tree *add* a dependency to a system where the ebuild is installed? That doesn't seem desirable. To me it seems like a simple data model bug that vdb does not get updated to reflect the new situation after step 2 above. > So, now user has package A installed which has unsatisfied > dependency on non-available package. What is the purpose of keeping only dependencies as-they-were when the package was installed, if the package manager does not somehow benefit from that information in the future? //Peter
pgp_7dQnFYlMN.pgp
Description: PGP signature
