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