On 28 July 2014 03:52, Rich Freeman <ri...@gentoo.org> wrote: > Why? Is this about removing an unused dependency? > > > 3. Gentoo simply tweaks the ebuild and doesn't bump [A] > > What is "[A]?" What ebuild was tweaked, and how was it tweaked? >
Here, "A" is the derived version of the ebuild of "Foo" the user installed, in the present dynamic deps situation. That is, Although user and tree have the same $PVR value, one has different DEPENDS, and my impression based on past discussions is in that scenario, the DEPENDS from /usr/portage/ take preceidence over VDB. Though perhaps it depends on your definition of "used". If your definition of "used" is "other things in portage needs it", then this case is satisfied by it being "used" by the world file. Users will likely know in such a scenario that they are "using" a thing that is no longer in tree, but if it no longer being "in tree" changes how its dependencies resolve for the worse. *Most* examples of this you will see will be resolved by pkgmoves munging the installed dependencies in VDB to cease to be broken. I guess, in a way, pkgmove and dynamic deps are the same problem from different perspectives. pkgmove is an instruction that "set( X ) that requires Y needs to change" and dynamic deps are "X requires set ( Y ) and needs to change." Just in the case of the former, the effect is made permanent as part of the sync, and in the case of the latter ( based on my understanding ) the effect is temporary ( bounded by the lifetime of the ebuild in /usr/portage ) and resolved at runtime for each and every merge .... ( Do correct me if I'm wrong about this ) -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
