Gentoo Archives: gentoo-dev

From: hasufell <hasufell@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Does the scm ebuild masking policy make sense for git?
Date: Tue, 09 Sep 2014 19:12:44
Message-Id: 540F511C.80703@gentoo.org
In Reply to: Re: [gentoo-dev] Does the scm ebuild masking policy make sense for git? by Jauhien Piatlicki
1 Jauhien Piatlicki:
2 >
3 > When I accept ~arch I expect that no live ebuilds will be built. I think other gentoo users expect the same.
4
5 Just because users are used to it doesn't make it better.
6
7 >
8 > Emerging live ebuild usually is quite a risky thing, so hiding such stuff behind dropped keywords is quite reasonable.
9 >
10
11 That's why you can mask them.
12
13 Hiding useful information from users is not reasonable.
14
15
16 The same flawed logic of empty KEYWORDS could actually be applied to any
17 ebuild variable.
18 You say "we can't test if it works for all these architectures reliably
19 and for every single commit".
20 Yeah, same goes for dependencies, license and even the description.
21 Because it's a live ebuild, all of them can change. KEYWORDS is no
22 special exception.

Replies