Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: Ulrich Mueller <ulm@g.o>, Zac Medico <zmedico@g.o>
Cc: gentoo-portage-dev@l.g.o, Joakim Tjernlund <Joakim.Tjernlund@××××××××.com>
Subject: Re: [gentoo-portage-dev] profile masking
Date: Fri, 14 Aug 2020 20:42:56
Message-Id: 18bb2b79-ff40-3759-8551-ee02050d9534@gentoo.org
In Reply to: Re: [gentoo-portage-dev] profile masking by Ulrich Mueller
1 On 8/14/20 1:08 PM, Ulrich Mueller wrote:
2 >>>>>> On Fri, 14 Aug 2020, Zac Medico wrote:
3 >
4 >> On 8/14/20 8:42 AM, Joakim Tjernlund wrote:
5 >>> Yes, I know I can add that in profile/package.mask but I am looking
6 >>> for the bigger picture here. This has to stop somehow, there need to
7 >>> be something that limits the mask scope to the repo/overlay it is
8 >>> defined.
9 >
10 >> The scope is already limited, but this overlay inherits the mask because
11 >> it has the gentoo repo as its master (either implicitly or via a masters
12 >> setting in metadata/layout.conf).
13 >
14 >> I suppose we could add an option to prevent this inheritance.
15 >
16 > Like an option in repos.conf or layout.conf?
17 >
18 > The problem I see with this is that preventing inheritance would disable
19 > files like license_groups or thirdpartymirrors. So overlays would have
20 > to maintain their own versions.
21
22 I've just tested, and it's possible to do this with a -* at the top of
23 the overlay/profiles/package.mask file, if we simply modify the the
24 grabfile_package function to allow the -* pass through (it currently
25 discards it as an invalid atom).
26
27 >>> I think a good start would be to consider /etc/portage the top
28 >>> profile and other subprofiles should be able to use the same features
29 >>> as /etc/portage.
30 >>>
31 >>> Portage could start supporting that now, but there would be a while
32 >>> until one can use them in Gentoo profile.
33 >
34 >> We've got this bug open for the ::repo atom support:
35 >
36 >> https://bugs.gentoo.org/651208
37 >
38 > I still believe that adding ::gentoo to every line in package.mask would
39 > be the wrong approach to the problem.
40
41 Of course, that would be silly. The per-repo package.mask scoping is
42 actually implemented internally by adding an implicit ::repo to each
43 atom in the package.mask file.
44 --
45 Thanks,
46 Zac

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-portage-dev] profile masking Zac Medico <zmedico@g.o>