Gentoo Archives: gentoo-dev

From: Brian Evans <grknight@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=...
Date: Tue, 02 Mar 2021 19:38:45
Message-Id: b3ce19c2-610c-abc1-3078-d4ebb93eab12@gentoo.org
In Reply to: Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=... by Alessandro Barbieri
1 On 3/2/2021 2:36 PM, Alessandro Barbieri wrote:
2 > Il Mar 2 Mar 2021, 20:03 Matt Turner <mattst88@g.o
3 > <mailto:mattst88@g.o>> ha scritto:
4 >
5 > On Tue, Mar 2, 2021 at 12:11 AM Michael Orlitzky <mjo@g.o
6 > <mailto:mjo@g.o>> wrote:
7 > >                                 why don't we just enforce putting
8 > each
9 > > keyword on a separate line instead, so that we don't have this
10 > problem
11 > > in the first place?
12 >
13 > Why don't we change 30 thousand ebuilds rather than use this script?
14 >
15 >
16 > IMO before this the keyword mechanism should be reworked to be three-state:
17 > 1 Arch known working
18 > 2 Arch known not working
19 > 3 Arch untested/status unknown
20 >
21 > And let the user choose to use packages from 3 or not
22 >
23 This is how it already is. 1 and 3 are common but 2 is uncommon except
24 for binary only packages.
25
26 Brian

Attachments

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