From: Zac Medico <zmedico@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] EAPI specification in ebuilds
Date: Tue, 10 Apr 2012 12:23:08 -0700 [thread overview]
Message-ID: <4F84889C.4020803@gentoo.org> (raw)
In-Reply-To: <20356.26282.371543.987108@a1i15.kph.uni-mainz.de>
On 04/10/2012 09:58 AM, Ulrich Mueller wrote:
>>>>>> On Tue, 10 Apr 2012, Brian Harring wrote:
>
>> On Tue, Apr 10, 2012 at 08:43:55AM -0700, Zac Medico wrote:
>>> We could make the ([A-Za-z0-9+_.-]*) group "optional", but treat it
>>> as an error if the group is missing. That way, the package manager
>>> can detect invalid assignments earlier, and can skip sourcing the
>>> ebuild in this case.
>
> Currently there isn't any ebuild in the tree that assigns an empty
> EAPI, so I think we can neglect any performance issues.
My intention was to detect EAPI assignments containing invalid
characters such as spaces or unicode characters. Either way, I agree
it's not really a performance issue. If it makes the specification too
complex for your liking, then I agree it's not worth doing.
--
Thanks,
Zac
next prev parent reply other threads:[~2012-04-10 19:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 7:40 [gentoo-pms] EAPI specification in ebuilds Ulrich Mueller
2012-04-06 17:29 ` Robin H. Johnson
2012-04-06 17:32 ` Brian Harring
2012-04-06 17:33 ` Ciaran McCreesh
2012-04-06 18:13 ` Ulrich Mueller
2012-04-06 18:08 ` Ciaran McCreesh
2012-04-06 18:57 ` David Leverton
2012-04-06 21:25 ` Ulrich Mueller
2012-04-06 21:56 ` David Leverton
2012-04-07 2:44 ` Ulrich Mueller
2012-04-10 10:53 ` Ulrich Mueller
2012-04-10 15:43 ` Zac Medico
2012-04-10 16:30 ` Brian Harring
2012-04-10 16:35 ` Zac Medico
2012-04-10 16:58 ` Ulrich Mueller
2012-04-10 19:23 ` Zac Medico [this message]
2012-04-10 19:25 ` Ciaran McCreesh
2012-04-10 20:13 ` Ulrich Mueller
2012-04-10 20:16 ` Ciaran McCreesh
2012-04-10 21:19 ` Ulrich Mueller
2012-04-10 21:41 ` Ciaran McCreesh
2012-04-10 22:11 ` Ulrich Mueller
2012-04-10 23:20 ` David Leverton
2012-04-11 8:04 ` Ulrich Mueller
2012-04-11 16:31 ` Zac Medico
2012-04-11 18:02 ` David Leverton
2012-04-11 18:22 ` Zac Medico
2012-04-12 11:55 ` Ulrich Mueller
2012-04-15 22:30 ` Zac Medico
2012-04-15 23:12 ` Ulrich Mueller
2012-05-13 18:23 ` David Leverton
2012-05-13 19:00 ` Ulrich Mueller
2012-05-13 19:11 ` [gentoo-pms] [PATCH 1/2] Clarify wording for EAPI parsing David Leverton
2012-05-13 19:35 ` Ulrich Mueller
2012-05-13 19:40 ` David Leverton
2012-05-13 20:46 ` Ulrich Mueller
2012-05-17 10:15 ` Ulrich Mueller
2012-05-13 19:12 ` [gentoo-pms] [PATCH 2/2] Require a space before the trailing comment David Leverton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F84889C.4020803@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-pms@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox