| 1 |
On Sun, Mar 18, 2012 at 09:50:29PM +0000, bugzilla-daemon@g.o wrote: |
| 2 |
> DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person |
| 3 |
> whose email is mentioned below. To comment on this bug, please visit: |
| 4 |
> https://bugs.gentoo.org/show_bug.cgi?id=402167 |
| 5 |
> |
| 6 |
> --- Comment #60 from Steve L <slong@××××××××××××××××××.uk> --- |
| 7 |
> (In reply to comment #54) |
| 8 |
> > > I can't really see that it's such a hardship for ebuild authors to use: |
| 9 |
> > > EAPI=token |
| 10 |
> > > |
| 11 |
> > > (no quotes, and no whitespace in the token, which is terminated by |
| 12 |
> > > whitespace.) |
| 13 |
> > |
| 14 |
> > And how many ebuilds follow that? |
| 15 |
> > |
| 16 |
> > Even if you change the entire tree, people will still get it wrong, since |
| 17 |
> > it's an arbitrary restriction that doesn't apply to anything else and has no |
| 18 |
> > obvious reason for being there. |
| 19 |
> |
| 20 |
> Fine, so we allow quoting. It still makes sense to specify the allowed format |
| 21 |
> of the EAPI name in PMS, just as is done for so many other tokens like keywords |
| 22 |
> or USE flags. After all, the EAPI name defines everything else that can happen, |
| 23 |
> so its omission seems surprising. |
| 24 |
|
| 25 |
Just curious... ignoring the EAPI discussion here, does anyone |
| 26 |
actually think moving HOMEPAGE to metadata.xml is a good idea? |
| 27 |
|
| 28 |
Personally I'd like to close that ticket, 'cept it's currently been |
| 29 |
hijacked by EAPI discussions. |
| 30 |
~brian |
Archives