1 |
>>>>> On Mon, 07 Sep 2020, Michael Orlitzky wrote: |
2 |
|
3 |
> On 2020-09-07 02:14, Michał Górny wrote: |
4 |
>> + <li> |
5 |
>> + Update all ebuilds not to reference the virtual. Since there is |
6 |
>> + no urgent need to remove the virtual from user systems |
7 |
>> + and the resulting rebuilds would be unnecessary, do not bump ebuilds |
8 |
>> + when replacing the dependency. |
9 |
>> + </li> |
10 |
|
11 |
> This has caused dependency resolution problems in the past. The PMS |
12 |
> implies a new revision, |
13 |
|
14 |
PMS says nothing about new revisions or revision bumps: |
15 |
|
16 |
$ grep -i "new revision" pms/*.tex |
17 |
$ grep -i bump pms/*.tex |
18 |
$ |
19 |
|
20 |
> the council said make a new revision, and the devmanual already says |
21 |
> make a new revision. [...] |
22 |
|
23 |
The devmanual [1] says that a revbump should be done when a new runtime |
24 |
dependency is added to an ebuild, but it doesn't say that for removal of |
25 |
a dependency. |
26 |
|
27 |
We are talking about the second case here, because the dependency on the |
28 |
virtual is being removed, while the dependency on its provider remains |
29 |
in place (it only changes from an indirect to a direct dependency). |
30 |
|
31 |
Ulrich |
32 |
|
33 |
[1] https://devmanual.gentoo.org/general-concepts/ebuild-revisions/index.html |