Bugzilla Bug 184219

Emacs support has been split off from sys-devel/autoconf into a separate
package app-emacs/autoconf-mode, see bug #184196.

Please (re)keyword both packages.

Target keywords:
                              |                           s     |
                              |                 p         p     |
                              |                 p         a   x |
                              |                 c         r   8 |
                              |                 -         c   6 |
                              | a a             m p     s -   - |
                              | l m   h i m m   a p s   p f   f |
                              | p d a p a 6 i p c c 3   a b x b |
                              | h 6 r p 6 8 p p o 6 9 s r s 8 s |
                              | a 4 m a 4 k s c s 4 0 h c d 6 d |
------------------------------+---------------------------------+
sys-devel/autoconf-2.61-r1    | ~ ~ ~ ~ ~ ~ ~ ~   ~ ~ ~ ~ ~ ~ ~ |
app-emacs/autoconf-mode-2.61  | ~ ~ ~ ~ ~     ~   ~ ~ ~ ~ ~ ~ ~ |

Test plan for app-emacs/autoconf-mode:
<http://overlays.gentoo.org/proj/emacs/wiki/test%20plans>

Why where keywords dropped in the first place? The autoconf code is still the
same yes?

Anyway, I've added fbsd keywords back.

(In reply to comment #2)
> Why where keywords dropped in the first place?

Because autoconf now PDEPENDS on autoconf-mode which is a new package.

> The autoconf code is still the same yes?

It is.

(In reply to comment #3)
> (In reply to comment #2)
> > Why where keywords dropped in the first place?
> 
> Because autoconf now PDEPENDS on autoconf-mode which is a new package.
> 
> > The autoconf code is still the same yes?
> 
> It is.
> 

Hmmmm. It strikes me that autoconf-mode could just inherit the same keywords as
it's codebase is already tested on the arches - otherwise the arches would have
the emacs USE flag masked in their profile.

So from my perspective this keywording is just a waste of everyones time -
unless you can demonstrate different.

(In reply to comment #4)
> So from my perspective this keywording is just a waste of everyones time -
> unless you can demonstrate different.

Sorry, I just tried to follow the usual rules, i.e. keywording for a new
package should be done by the arch teams.

If you really want to cut it short, I would suggest that the arch teams
(everyone except bsd) go straight to stable.

~alpha/~ia64 done

AMD64: I get a few 'expected failure' messages on the tests, are these
critical?

(In reply to comment #7)
> AMD64: I get a few 'expected failure' messages on the tests, are these
> critical?

Should be the same as for autoconf-2.61 (which is stable on amd64) since that
part of the code has not changed.

yup, it is. Are these actual errors, or that the test was expected to fail and
did so?

added ~ppc64

(In reply to comment #4)
> Hmmmm. It strikes me that autoconf-mode could just inherit the same keywords
> as it's codebase is already tested on the arches - otherwise the arches would
> have the emacs USE flag masked in their profile.
>
> So from my perspective this keywording is just a waste of everyones time -
> unless you can demonstrate different.

<vapier> same like autotools, sure                                      [00:07]
<ulm> you think it's o.k. to carry gettext's KEYWORDS over to the new package?
<ulm> uberlord has complained about how I handled it for autotools      [00:08]
<vapier> carrying KEYWORDs is fine
<vapier> it should behave the same for all arches

So I follow uberlord's and vapier's advice and (re-)add ~amd64, ~arm, ~hppa,
~ppc, ~s390, ~sh, ~sparc, and ~sparc-fbsd.

See you next month for stabilising. ;)