Denis Dupeyron posted on Mon, 28 Jul 2014 18:15:20 -0600 as excerpted: > On Mon, Jul 28, 2014 at 12:41 AM, Samuli Suominen <ssuomi...@gentoo.org> > wrote: >> x265-1.2.ebuild: KEYWORDS="~amd64 ~arm ~x86" >> x265-1.3.ebuild: KEYWORDS="~amd64 ~x86" >> x265-9999.ebuild: KEYWORDS="~amd64 ~x86" >> >> As in... You forgot to add ~arm to -9999.ebuild > > Wait, what? Live ebuilds are keyworded now?
AFAIK, gentoo policy is that live ebuilds should always be masked so as never to be automatically pulled in without a deliberate unmasking of the live ebuild, but whether that's masked due to lack of keywords (ebuild), or due to hard-mask (package.mask) is I believe up to the maintainer. For packages like this one where normal version-bumps start with the live ebuild (which after all should have been updated as development proceeded, upstream), simply copying it to the appropriate version-number ebuild, keeping it ~arch-keyworded on all archs where the non-live version is at least ~arch-keyworded, and using package.mask to force the masking, makes the most sense since then a version bump can literally amount to no more than an ebuild copy and manifest (tho obviously the maintainer will test it too, but ideally won't have to actually touch the content of the file). -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
