* [gentoo-pms] Re: [Bug 402167] [Future EAPI] Move HOMEPAGE to metadata.xml
[not found] ` <bug-402167-48044-N6Orhu3id6@http.bugs.gentoo.org/>
@ 2012-03-19 22:46 ` Brian Harring
0 siblings, 0 replies; only message in thread
From: Brian Harring @ 2012-03-19 22:46 UTC (permalink / raw
To: gentoo-pms
On Sun, Mar 18, 2012 at 09:50:29PM +0000, bugzilla-daemon@gentoo.org wrote:
> DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person
> whose email is mentioned below. To comment on this bug, please visit:
> https://bugs.gentoo.org/show_bug.cgi?id=402167
>
> --- Comment #60 from Steve L <slong@rathaus.eclipse.co.uk> ---
> (In reply to comment #54)
> > > I can't really see that it's such a hardship for ebuild authors to use:
> > > EAPI=token
> > >
> > > (no quotes, and no whitespace in the token, which is terminated by
> > > whitespace.)
> >
> > And how many ebuilds follow that?
> >
> > Even if you change the entire tree, people will still get it wrong, since
> > it's an arbitrary restriction that doesn't apply to anything else and has no
> > obvious reason for being there.
>
> Fine, so we allow quoting. It still makes sense to specify the allowed format
> of the EAPI name in PMS, just as is done for so many other tokens like keywords
> or USE flags. After all, the EAPI name defines everything else that can happen,
> so its omission seems surprising.
Just curious... ignoring the EAPI discussion here, does anyone
actually think moving HOMEPAGE to metadata.xml is a good idea?
Personally I'd like to close that ticket, 'cept it's currently been
hijacked by EAPI discussions.
~brian
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-03-19 23:46 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <bug-402167-48044@http.bugs.gentoo.org/>
[not found] ` <bug-402167-48044-N6Orhu3id6@http.bugs.gentoo.org/>
2012-03-19 22:46 ` [gentoo-pms] Re: [Bug 402167] [Future EAPI] Move HOMEPAGE to metadata.xml Brian Harring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox