From: Zac Medico <zmedico@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] [PATCH] EAPI must be at least a single char.
Date: Sun, 30 Sep 2012 17:48:38 -0700 [thread overview]
Message-ID: <5068E866.3030806@gentoo.org> (raw)
In-Reply-To: <20584.49976.485460.399575@a1i15.kph.uni-mainz.de>
On 09/30/2012 03:10 PM, Ulrich Mueller wrote:
>>>>>> On Sun, 30 Sep 2012, Zac Medico wrote:
>
>>> tries to write a PM, likely fucking that up. If what you were
>>> saying was the actual intention behind it, that assignment would've
>>> just been along the lines of EAPI=("[^"]*"|'[^']*'|[^\t ]); aka
>>> "here's how you grab what looks like an EAPI assignment".
>
>> I would have preferred a regex that just matches any assignment like
>> this, but didn't feel like bikeshedding it,
>
> I doesn't really matter what the regexp is, as long as it matches a
> superset of the allowed EAPI syntax. Unknown or invalid EAPIs that the
> regexp doesn't match will still be rejected, because the results from
> parsing and from sourcing the ebuild don't agree.
>
> And it is practically impossible to find a regexp that would match all
> valid bash assignments. You would have to handle backslash escapes,
> dollar signs, and whatnot.
Still, it might make sense to replace ([A-Za-z0-9+_.-]*) with (.*),
since that should work fine in practice. The spec is fine with me as it
is, but I don't think a change like this would hurt.
--
Thanks,
Zac
next prev parent reply other threads:[~2012-10-01 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 8:28 [gentoo-pms] [PATCH] EAPI must be at least a single char Brian Harring
2012-09-30 9:13 ` Ulrich Mueller
2012-09-30 19:44 ` Brian Harring
2012-09-30 19:52 ` Zac Medico
2012-09-30 22:10 ` Ulrich Mueller
2012-10-01 0:48 ` Zac Medico [this message]
2012-09-30 22:22 ` Brian Harring
2012-10-01 0:25 ` Zac Medico
2012-10-01 7:15 ` Ulrich Mueller
2012-10-01 16:33 ` Zac Medico
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=5068E866.3030806@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