1 |
On Wed, Jul 30, 2014 at 07:29:22PM +0200, Michael Haubenwallner wrote: |
2 |
> |
3 |
> Am 2014-07-30 14:33, schrieb Samuli Suominen: |
4 |
> > |
5 |
> > There is no need to package.mask if proper if -logic is used, like, for |
6 |
> > example, |
7 |
> > |
8 |
> > if [[ ${PV} == 9999* ]]; then |
9 |
> > inherit git-r3 |
10 |
> > KEYWORDS="" |
11 |
> > else |
12 |
> > KEYWORDS="~amd64 ~arm ~arm64 ~x86" |
13 |
> > fi |
14 |
> > |
15 |
> > Then you can just `cp foo-9999.ebuild foo-1.2.3.ebuild` and it'll have |
16 |
> > the KEYWORDS |
17 |
> > ready, and 1.2.3 and 9999 ebuilds can be identical |
18 |
> |
19 |
> Which instance of the KEYWORDS line is touched by the ekeyword tool these days? |
20 |
> |
21 |
> To have ekeyword touch the else-part in the release ebuild, what about this: |
22 |
> |
23 |
> if [[ ${PV} == 9999* ]]; then |
24 |
> inherit vcs... |
25 |
> :; KEYWORDS="" |
26 |
> else |
27 |
> KEYWORDS="..." |
28 |
> fi |
29 |
|
30 |
Actually you can even go further since KEYWORDS is an optional variable: |
31 |
|
32 |
if [[ ${PV} == 9999* ]]; then |
33 |
inherit vcs... |
34 |
else |
35 |
KEYWORDS="..." |
36 |
fi |
37 |
|
38 |
William |