From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New GLEP: file installation masks
Date: Fri, 20 May 2016 16:00:38 -0400 [thread overview]
Message-ID: <bde16313-c379-d9c7-2546-f05cade648e9@gentoo.org> (raw)
In-Reply-To: <20160520174908.514ddb4e@pomiocik>
[-- Attachment #1.1: Type: text/plain, Size: 1445 bytes --]
On 20/05/16 11:49 AM, Michał Górny wrote:
> On Fri, 20 May 2016 11:40:39 -0400
> Michael Orlitzky <mjo@gentoo.org> wrote:
>
>> On 05/20/2016 11:34 AM, Daniel Campbell wrote:
>>>
>>> ...and the user has this in their install.mask file:
>>>
>>> [bash-completion]
>>> path=/some/other/path
>>> desc=some other description
>>>
>>
>> I don't think that's allowed; the groups are specified by each
>> repository's metadata/install-mask.conf, not by the users.
>>
>> Although, you can ask the same question about overlays that have
>> group-name clashes. Is that an error, or would we use the one from the
>> overlay?
>
> Oh, you are correct. Originally I planned to handle that, and I forgot
> about it.
>
> Since there can be multiple paths, we have two options: either
> override, or amend like systemd does with *.d files. I think the former
> would be less surprising.
>
> Override is simple -- entry from next file overrides previous,
> and discards all data.
>
> Amending is harder. Description from next file overrides former, but
> paths are appended. But there is special 'path=' (empty) that discards
> all previous values and starts over. I don't think that's really a good
> idea for repos.
I'd vote override, simply because it would match the same behaviour
seen with eclasses and we could leverage the same 'masters =' in
repos.conf to manage order when dealing with multiple repos.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2016-05-20 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 14:01 [gentoo-dev] [RFC] New GLEP: file installation masks Michał Górny
2016-05-20 15:12 ` Michael Orlitzky
2016-05-20 15:21 ` Michał Górny
2016-05-20 15:30 ` Michael Orlitzky
2016-05-20 15:44 ` Michał Górny
2016-05-20 16:15 ` Michael Orlitzky
2016-05-20 16:48 ` Michał Górny
2016-05-20 17:34 ` Michael Orlitzky
2016-05-29 12:54 ` Michał Górny
2016-05-20 15:34 ` Daniel Campbell
2016-05-20 15:40 ` Michael Orlitzky
2016-05-20 15:49 ` Michał Górny
2016-05-20 20:00 ` Ian Stakenvicius [this message]
2016-05-20 21:11 ` Michał Górny
2016-06-08 5:26 ` [gentoo-dev] " Ulrich Mueller
2016-06-08 6:37 ` Michał Górny
2016-06-08 7:17 ` Ulrich Mueller
2016-06-08 8:01 ` Michał Górny
2016-06-08 8:33 ` Ulrich Mueller
2016-06-08 13:14 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bde16313-c379-d9c7-2546-f05cade648e9@gentoo.org \
--to=axs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox