| 1 |
>>>>> On Sun, 21 Sep 2014, Peter Stuge wrote: |
| 2 |
|
| 3 |
> Jonathan Callen wrote: |
| 4 |
>> the correct response would be to ensure that the final commit |
| 5 |
>> pushed (whether it be a merge commit or rebased) contains the |
| 6 |
>> stabilization for both arches |
| 7 |
|
| 8 |
> I think this is one of the things to check in a post-receive or |
| 9 |
> post-update hook. What is the easiest way to access keywords out of |
| 10 |
> an ebuild - which does *not* require sourcing the ebuild in a shell? |
| 11 |
|
| 12 |
A quick scan of the tree shows that combinations of any of the |
| 13 |
following would have to be handled: |
| 14 |
- leading whitespace |
| 15 |
- double or single quotes, or no quotation marks at all |
| 16 |
- continuation lines, with or without backslash |
| 17 |
- comments following the keywords assignment |
| 18 |
- keywords inherited from an eclass |
| 19 |
|
| 20 |
Of course, there is no guarantee that devs don't invent something new |
| 21 |
that isn't in above list. :) So I'd say there is no sane way other |
| 22 |
than sourcing with bash, unless we want to restrict by policy what is |
| 23 |
allowed as KEYWORDS syntax. |
| 24 |
|
| 25 |
Ulrich |
Archives