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