| 1 |
On Sunday 13 Apr 2014 22:48:43 Rick Zero_Chaos Farina wrote: |
| 2 |
|
| 3 |
> The real answer is almost certainly dynamic-deps. The binary packages |
| 4 |
> store the deps from BUILD time, while when you are installing things |
| 5 |
> live, it allows the current ebuilds to update the deps even for |
| 6 |
> installed packages. |
| 7 |
> |
| 8 |
> That means, after you install a package, if the deps in the ebuild are |
| 9 |
> changed, portage will take that into account for source builds, but |
| 10 |
> binary packages are LOCKED to the deps from the time they were built. |
| 11 |
> |
| 12 |
> Why dynamic-deps aren't available no matter what? Now that's a great |
| 13 |
> question... |
| 14 |
|
| 15 |
But I'd only just finished an emerge -eb world on the build host to re-create |
| 16 |
the packages. Nothing could have changed in the meantime. |
| 17 |
|
| 18 |
-- |
| 19 |
Regards |
| 20 |
Peter |
Archives