On Mon, 14 Apr 2014 14:32:49 +0100, Peter Humphrey wrote: > > That means, after you install a package, if the deps in the ebuild are > > changed, portage will take that into account for source builds, but > > binary packages are LOCKED to the deps from the time they were built. > > > > Why dynamic-deps aren't available no matter what? Now that's a great > > question... > > But I'd only just finished an emerge -eb world on the build host to > re-create the packages. Nothing could have changed in the meantime.
Those extra packages are build deps. When you emerge -k, you aren't doing any building, so the build deps aren't needed. They need not even be installed on that box, only on the one doing the building. -- Neil Bothwick Barnum was wrong....it's more like every 30 seconds!
signature.asc
Description: PGP signature
