From: Brian Harring <ferringb@gmail.com>
To: Walter Dnes <waltdnes@waltdnes.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFD : .ebuild is only bash
Date: Tue, 13 Mar 2012 00:03:34 -0700 [thread overview]
Message-ID: <20120313070334.GK7579@localhost> (raw)
In-Reply-To: <20120313064113.GA23544@waltdnes.org>
On Tue, Mar 13, 2012 at 02:41:13AM -0400, Walter Dnes wrote:
> On Mon, Mar 12, 2012 at 05:12:28PM +0000, Ciaran McCreesh wrote
>
> > This whole thing is just an exercise in trying to find excuses not to
> > use GLEP 55.
>
> A filename should not be (ab)used as a database. The main argument for
> GLEP 55 is that it would make ebuild-processing generic. I.e. making
> ebuild info available to whatever future ebuild processor replacement
> for bash was used. A couple of comments...
>
> 1) Let's talk generic. Right now, we're talking about EAPI. In future,
> what other (meta)data and characteristics will we need to know? What
> else will be tacked onto the filename? EAPI, and any other critical
> (meta)data should be declared early on in the ebuild. That's what the
> ebuild is for.
>
> 2) Any potential ebuild processor that's incapable of looking for regex
> "^EAPI=" in a textfile, amd parsing the numbers that follow, has no
> business being used to process ebuilds.
Perfectly valid, if stupid, bash:
EAPI=3
EAPI=4
Which is the PM to choose? Because if your answer is "the first",
then you need to keep in mind that any following code (including
eclasses that test eapi) will be seeing the second during sourcing.
Nice little gotcha, that one.
I'm aware people have suggested "make EAPI readonly" to try and deal
w/ this; that however means it'll break any PM that uses eval for
loading the ebuild, and means that every ebuild sourcing for phase
running will throw a complaint about EAPI being readonly.
I don't hugely expect PMs to screw up the ordering of which to chose,
although it exists; trying to ban secondary settings is also an
approach... but all of it points to the fact it's a fricking hack and
isn't really worth doing.
If we're going to redo EAPI, redo it right. Don't half ass it- this
time around we're not forced to make compromises.
Viewing it that way, this grep hack shouldn't be on the table as a
viable option.
~harring
next prev parent reply other threads:[~2012-03-13 7:05 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAATnKFD=9VEkpUcABbhHbAu96Qn+dP+YEuUu2YCqDUNKUxe+Cw@mail.gmail.com>
2012-03-12 15:57 ` [gentoo-dev] RFD : .ebuild is only bash Kent Fredric
2012-03-12 15:59 ` Ciaran McCreesh
2012-03-12 16:51 ` Rich Freeman
2012-03-12 17:05 ` Ulrich Mueller
2012-03-12 17:12 ` Ciaran McCreesh
2012-03-12 17:17 ` Michael Orlitzky
2012-03-12 17:22 ` Ciaran McCreesh
2012-03-12 17:30 ` Zac Medico
2012-03-12 17:22 ` Zac Medico
2012-03-12 18:00 ` Ulrich Mueller
2012-03-12 18:04 ` Ciaran McCreesh
2012-03-12 18:17 ` Ulrich Mueller
2012-03-12 18:28 ` Ciaran McCreesh
2012-03-12 18:50 ` Ulrich Mueller
2012-03-12 18:58 ` Ian Stakenvicius
2012-03-12 19:01 ` Ciaran McCreesh
2012-03-12 19:49 ` Ulrich Mueller
2012-03-12 20:10 ` Ciaran McCreesh
2012-03-12 20:21 ` James Broadhead
2012-03-12 21:14 ` Ulrich Mueller
2012-03-12 21:28 ` Kent Fredric
2012-03-12 21:49 ` Alec Warner
2012-03-12 22:02 ` Mike Gilbert
2012-03-12 22:37 ` Kent Fredric
2012-03-12 22:53 ` Alec Warner
2012-03-13 6:31 ` [gentoo-dev] " Duncan
2012-03-12 22:55 ` [gentoo-dev] " James Broadhead
2012-03-13 6:06 ` Ulrich Mueller
2012-03-12 22:06 ` James Broadhead
2012-03-12 22:17 ` Alec Warner
2012-03-12 19:00 ` Ciaran McCreesh
2012-03-12 19:38 ` Ulrich Mueller
2012-03-12 19:42 ` Ciaran McCreesh
2012-03-13 20:33 ` Brian Harring
2012-03-13 0:51 ` Patrick Lauer
2012-03-12 18:29 ` Kent Fredric
2012-03-13 4:31 ` Brian Harring
2012-03-13 5:14 ` Kent Fredric
2012-03-13 6:22 ` Brian Harring
2012-03-13 16:10 ` Wulf C. Krueger
2012-03-13 19:08 ` Brian Harring
2012-03-13 7:11 ` [gentoo-dev] " Duncan
2012-03-12 18:01 ` [gentoo-dev] " Michał Górny
2012-03-12 17:53 ` Ulrich Mueller
2012-03-12 18:03 ` Kent Fredric
2012-03-13 0:46 ` Patrick Lauer
2012-03-13 6:41 ` Walter Dnes
2012-03-13 6:56 ` Kent Fredric
2012-03-13 7:03 ` Brian Harring [this message]
2012-03-13 8:50 ` Ulrich Mueller
2012-03-13 15:52 ` Zac Medico
2012-03-13 7:30 ` Ciaran McCreesh
2012-03-14 0:29 ` Walter Dnes
2012-03-14 0:48 ` Michael Orlitzky
2012-03-14 1:42 ` Brian Harring
2012-03-14 2:05 ` Zac Medico
2012-03-14 2:23 ` Michael Orlitzky
2012-03-14 2:36 ` Zac Medico
2012-03-14 2:38 ` Michael Orlitzky
2012-03-14 2:38 ` Brian Harring
2012-03-14 2:47 ` Zac Medico
2012-03-12 16:56 ` Ulrich Mueller
2012-03-12 18:04 ` Michał Górny
2012-03-13 6:29 ` Richard Yao
2012-03-13 11:52 ` Rich Freeman
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=20120313070334.GK7579@localhost \
--to=ferringb@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=waltdnes@waltdnes.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