On 30/07/14 14:48, Luis Ressel wrote:
> On Wed, 30 Jul 2014 09:38:16 +0000 (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>
>> In the context of that policy and a content-touchless-bump goal, I
>> suppose I'd script the bump, pulling keywords from the highest
>> previous version, prepending the ~ as necessary and inserting them in
>> the keywords line after copying the file from the live-ebuild . That
>> wouldn't be content-touchless, but the touch would be automated so as
>> to avoid mistakes and unnecessary work.
> That proposed script reminds me of http://xkcd.com/1319/. ;)
>
> I think I'd rather go with the original workflow. Okay, perhaps
> package.masking -9999 is a bit uncommon and clutters package.mask, but
> it's not all *that* bad and it eases the workflow.
>
>
> Regards,
> Luis Ressel
There is no need to package.mask if proper if -logic is used, like, for
example,
if [[ ${PV} == 9999* ]]; then
inherit git-r3
KEYWORDS=""
else
KEYWORDS="~amd64 ~arm ~arm64 ~x86"
fi
Then you can just `cp foo-9999.ebuild foo-1.2.3.ebuild` and it'll have
the KEYWORDS
ready, and 1.2.3 and 9999 ebuilds can be identical
That's what this thread was originally about... That's how x265's ebuild
work, just like eg.
media-libs/xine-lib or sys-fs/udev ebuilds does
(It just seemed this was unclear to some replying in this thread.)
- Samuli
