1 |
On Thu, 17 Sep 2015 20:14:59 +0100 |
2 |
Markos Chandras <hwoarang@g.o> wrote: |
3 |
> could someone explain what the dynamic dependencies are in the context |
4 |
> of portage and ebuilds? because that does seem to be something |
5 |
> portage-internal specific in the way it handles changes in {,R}DEPEND |
6 |
> without revbumps. Where is this thing documented in the first place? |
7 |
|
8 |
Sometimes, Portage will sort of use the dependencies specified in an |
9 |
ebuild rather than the dependencies specified in VDB for certain |
10 |
operations under certain conditions and certain phases of the moon, |
11 |
except when it doesn't. This is a quirk left over from the olden days, |
12 |
when Portage could only handle the existence of one version of any given |
13 |
package, and so couldn't cope with there being something called foo-1.2 |
14 |
in VDB and something else called foo-1.2 in the tree. This bug was |
15 |
largely fixed when env saving meant that eclasses no longer had to |
16 |
remain compatible with things in VDB, but traces of it still remain to |
17 |
cause confusion. |
18 |
|
19 |
-- |
20 |
Ciaran McCreesh |