On Mon, 14 Apr 2014 14:43:33 +0100 Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> Many thanks for that little bit of magic. I've incorporated it into a > simple script to find all the missed packages and list their atoms in > a form suitable for piping into emerge. You might not want to do that; those are _build_ dependencies, not _runtime_ dependencies. You don't need them for the package to run. > I still think this is bad behaviour by portage. If portage's > environment is identical in the two cases and I tell it to emerge > -ek, the results should be identical to those if I tell it to emerge > -e. I know that -e means "empty- tree" but that sounds to me exactly > like "everything", so that's what I expect to get. It is correct behaviour; `emerge -ek` is similar to `emerge -e ; emerge -c --with-bdeps=n`, where the `emerge -c --with-bdeps=n` unmerges the build dependencies after the packages were build. As they are no longer needed after that part; that is, if you don't intend to rebuild them. > Thanks again to both of you - at least I can now be sure that I've > rebuilt everything when I think I have. I hate to think how many > things I've missed in the past. No problem; be happy to now know you don't need that what misses. :) -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
