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