Re: [gentoo-dev] New tool: merge-driver-ekeyword automatically resolves git merge conflicts involving KEYWORDS=...

[Matt Turner]

On Tue, Mar 2, 2021 at 2:36 PM Alessandro Barbieri
<lssndrbarbieri@×××××.com> wrote:
>
> Il Mar 2 Mar 2021, 20:03 Matt Turner <mattst88@g.o> ha scritto:
>>
>> On Tue, Mar 2, 2021 at 12:11 AM Michael Orlitzky <mjo@g.o> wrote:
>> >                                 why don't we just enforce putting each
>> > keyword on a separate line instead, so that we don't have this problem
>> > in the first place?
>>
>> Why don't we change 30 thousand ebuilds rather than use this script?
>
>
> IMO before this the keyword mechanism should be reworked to be three-state:
> 1 Arch known working
> 2 Arch known not working
> 3 Arch untested/status unknown
>
> And let the user choose to use packages from 3 or not

Are you actually replying to me? I was restating mjo's question to
demonstrate the absurdity, not suggesting a different course of
action.