| 1 |
On 20/05/16 11:49 AM, Michał Górny wrote: |
| 2 |
> On Fri, 20 May 2016 11:40:39 -0400 |
| 3 |
> Michael Orlitzky <mjo@g.o> wrote: |
| 4 |
> |
| 5 |
>> On 05/20/2016 11:34 AM, Daniel Campbell wrote: |
| 6 |
>>> |
| 7 |
>>> ...and the user has this in their install.mask file: |
| 8 |
>>> |
| 9 |
>>> [bash-completion] |
| 10 |
>>> path=/some/other/path |
| 11 |
>>> desc=some other description |
| 12 |
>>> |
| 13 |
>> |
| 14 |
>> I don't think that's allowed; the groups are specified by each |
| 15 |
>> repository's metadata/install-mask.conf, not by the users. |
| 16 |
>> |
| 17 |
>> Although, you can ask the same question about overlays that have |
| 18 |
>> group-name clashes. Is that an error, or would we use the one from the |
| 19 |
>> overlay? |
| 20 |
> |
| 21 |
> Oh, you are correct. Originally I planned to handle that, and I forgot |
| 22 |
> about it. |
| 23 |
> |
| 24 |
> Since there can be multiple paths, we have two options: either |
| 25 |
> override, or amend like systemd does with *.d files. I think the former |
| 26 |
> would be less surprising. |
| 27 |
> |
| 28 |
> Override is simple -- entry from next file overrides previous, |
| 29 |
> and discards all data. |
| 30 |
> |
| 31 |
> Amending is harder. Description from next file overrides former, but |
| 32 |
> paths are appended. But there is special 'path=' (empty) that discards |
| 33 |
> all previous values and starts over. I don't think that's really a good |
| 34 |
> idea for repos. |
| 35 |
|
| 36 |
|
| 37 |
I'd vote override, simply because it would match the same behaviour |
| 38 |
seen with eclasses and we could leverage the same 'masters =' in |
| 39 |
repos.conf to manage order when dealing with multiple repos. |
Archives