On Sunday 13 Apr 2014 22:48:43 Rick Zero_Chaos Farina wrote: > The real answer is almost certainly dynamic-deps. The binary packages > store the deps from BUILD time, while when you are installing things > live, it allows the current ebuilds to update the deps even for > installed packages. > > 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. -- Regards Peter
