1 |
On Tue, Oct 3, 2017 at 7:05 AM, Ulrich Mueller <ulm@g.o> wrote: |
2 |
> |
3 |
> In addition, Portage doesn't support empty groups since 2011. That for |
4 |
> itself is not an argument to change PMS, but it shows that there is no |
5 |
> need for the construct. |
6 |
> |
7 |
|
8 |
If the behavior of portage doesn't match the specification in PMS that |
9 |
is reason enough to change one or the other. The purpose of PMS is to |
10 |
document how package managers are supposed to behave. |
11 |
|
12 |
You could: |
13 |
|
14 |
1. Change portage to behave as PMS specifies. |
15 |
2. Change PMS to specify portage's behavior. |
16 |
3. Change PMS to make the behavior explicitly undefined. |
17 |
|
18 |
Sure, this might be a lower-priority bug but this seems like a valid |
19 |
one. What is the point in having a specification if we don't actually |
20 |
specify what we're doing? |
21 |
|
22 |
-- |
23 |
Rich |