| 1 |
>>>>> On Tue, 22 Jul 2014, Martin Vaeth wrote: |
| 2 |
|
| 3 |
> Ulrich Mueller <ulm@g.o> wrote: |
| 4 |
>> Other problems appear, though. Documentation is installed in a |
| 5 |
>> ${PF} subdir, so install locations actually do change when updating |
| 6 |
>> the minor revision. |
| 7 |
|
| 8 |
> Yes, the minor revisions should not be exported into the variables |
| 9 |
> of ebuild.sh. I had forgotten this. |
| 10 |
|
| 11 |
That doesn't help. Imagine there is cat/foo-1 and the minor revision |
| 12 |
is bumped. The new ebuild is cat/foo-1-r0.1 then, and PF changes even |
| 13 |
if the minor revision is ignored (namely, from foo-1 to foo-1-r0). |
| 14 |
|
| 15 |
> Actually, I still think that implementing dynamic deps correctly |
| 16 |
> would be better, but minor revisions do not exclude this |
| 17 |
> and are probably simpler to implement. |
| 18 |
|
| 19 |
The PM could just update the VDB whenever it detects that the metadata |
| 20 |
of the ebuild has changed (relative to the VDB). You can get that |
| 21 |
without introducing the additional complication of minor revisions. |
| 22 |
|
| 23 |
Ulrich |
Archives