From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-50202-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1S6uwy-0001ZN-NA
for garchives@archives.gentoo.org; Mon, 12 Mar 2012 02:25:29 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 83BD4E0B07;
Mon, 12 Mar 2012 02:25:20 +0000 (UTC)
Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181])
by pigeon.gentoo.org (Postfix) with ESMTP id 9DBC3E0AF8
for <gentoo-dev@lists.gentoo.org>; Mon, 12 Mar 2012 02:24:55 +0000 (UTC)
Received: by werm13 with SMTP id m13so3249004wer.40
for <gentoo-dev@lists.gentoo.org>; Sun, 11 Mar 2012 19:24:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type
:content-transfer-encoding:x-gm-message-state;
bh=xy3upbDAdblC9zCkuD7Zfy+y0HjzcayXms6KGv76PQM=;
b=W3hH/Dd0dYpdjl6iVSLdHibhgoJKu8yiGjRctMC5/vHVm448T1lOixfrPREvVKnHfc
f5QrmuaPuEVPBHiatQt40RojUBx3zzRM9JrQ1tmFT6R2eCdK49uDygPSMD03+RjIGFJ9
eqfkUo3QDoiNDCkpZnYlRi1POqpHQfQtYvixvQ2a0m0ExqLMolLqnD/L4LDqWZmLJvWC
CEphMQbHrBMmyw+p/tecxz7Z2415qJCi6ly1qhEOm0ld0nfVyM/XpNiCx6HJSK2XrH4g
kheYWRh9YJmY9F9v71EP30tTzcuGFVuDN8Oavwm/wVNRsZt97QetlKf/N+7XJ9x7lTVw
iLVQ==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.180.19.37 with SMTP id b5mr23318880wie.9.1331519094713; Sun,
11 Mar 2012 19:24:54 -0700 (PDT)
Sender: antarus@scriptkitty.com
Received: by 10.227.5.138 with HTTP; Sun, 11 Mar 2012 19:24:54 -0700 (PDT)
In-Reply-To: <CAGfcS_=+7E-=zTMLEEFwM8xG4R21AJ3xWaS_HCE8P7PUEtNSyA@mail.gmail.com>
References: <4F58FC55.7070005@orlitzky.com>
<20120308184820.108fc30c@googlemail.com>
<4F592612.6050203@orlitzky.com>
<20120309060424.09cdce1e@pomiocik.lan>
<4F599692.9050503@orlitzky.com>
<20120309172921.281ee5a0@pomiocik.lan>
<4F5A368D.2020605@orlitzky.com>
<20314.14772.897891.110368@a1i15.kph.uni-mainz.de>
<4F5A3E6C.4040900@orlitzky.com>
<4F5A4246.8080605@gentoo.org>
<20120312020344.GE7579@localhost>
<CAGfcS_=+7E-=zTMLEEFwM8xG4R21AJ3xWaS_HCE8P7PUEtNSyA@mail.gmail.com>
Date: Sun, 11 Mar 2012 19:24:54 -0700
X-Google-Sender-Auth: cBP2NlhJ-mEBtjJdV9h9u9YtINk
Message-ID: <CAAr7Pr9X=DFJcrAZLS_3bn2TVqm46tKsH5Sk6b4UAuKJYaVAfA@mail.gmail.com>
Subject: Re: [gentoo-dev] RFD: EAPI specification in ebuilds
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnYuYWEce+2jsl6Ssaz/AJSGg2h+7idzVrmq++cXaxR7jonvqB6WAwKOXvYv4u0MW3NUQIJ
X-Archives-Salt: 2bbe4014-a0b4-4aa1-b6e6-aad66ef56fda
X-Archives-Hash: 46878807e95c008ca797278719525045
On Sun, Mar 11, 2012 at 7:20 PM, Rich Freeman <rich0@gentoo.org> wrote:
> On Sun, Mar 11, 2012 at 10:03 PM, Brian Harring <ferringb@gmail.com> wrot=
e:
>> Pragmatic reality, the eapi function actually would work fine. =C2=A0As
>> pointed out elsewhere, bash parses as it goes- which isn't going to
>> change.
>
> Unless the ebuild isn't written in bash...
I'd opt for a different extension in that case actually.
>
> How do you source the ebuild if you don't know what to use to source
> it? =C2=A0How do you know what to use to source it if you don't know the
> EAPI? =C2=A0Right now all the existing EAPIs use bash, but there is no
> reason the file couldn't be xml, or python, or just about anything
> else.
>
> If we want to allow for that kind of flexibility, then it might make
> sense to go ahead and state that our convention is to stick EAPI=3D5 in
> one of the first few lines of the ebuild, or inside a comment, but
> also go a step further and state that the text "EAPI=3D" cannot appear
> elsewhere in the ebuild (or perhaps within the first 10 lines). =C2=A0Jus=
t
> about any file format we might use would allow us to make "EAPI=3D"
> appear in it, but not all could guarantee that it would occur at the
> start of a line, or at the start of a line immediately after a #.
>
> In any case, I can really see the KISS value in a very rigid syntax
> that is trivial to parse. =C2=A0Stuff like this almost makes me wish our
> ebuilds already were xml files or such, with bash embedded inside
> sections. =C2=A0Finding a particular tag in an xml file is trivial as the
> fundamentals haven't changed in 15 years.
I will stab the next person who suggests 'xml-like ebuilds.'
-A
>
> Rich
>