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 ) id 1S71Dy-0005Gx-EJ for garchives@archives.gentoo.org; Mon, 12 Mar 2012 09:07:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 46FB1E0979; Mon, 12 Mar 2012 09:07:13 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id D1B76E0980 for ; Mon, 12 Mar 2012 09:06:39 +0000 (UTC) Received: from pomiocik.lan (159-205-88-242.adsl.inetia.pl [159.205.88.242]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 2AE3C1BC017; Mon, 12 Mar 2012 09:06:37 +0000 (UTC) Date: Mon, 12 Mar 2012 10:09:04 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: ciaran.mccreesh@googlemail.com Subject: Re: [gentoo-dev] RFD: EAPI specification in ebuilds Message-ID: <20120312100904.55b1a577@pomiocik.lan> In-Reply-To: <20120312083019.3d38ffa0@googlemail.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> <4F5DA0FE.1070405@gentoo.org> <20120312092711.7dbd969f@pomiocik.lan> <20120312083019.3d38ffa0@googlemail.com> Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/n5PyOtHbp0X/JzN1SXOfezU"; protocol="application/pgp-signature" X-Archives-Salt: 4e2f64c5-248b-4e3f-882a-ebcb526aef89 X-Archives-Hash: 2b80d4b08961a0a1e9e39425c7a8db43 --Sig_/n5PyOtHbp0X/JzN1SXOfezU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 12 Mar 2012 08:30:19 +0000 Ciaran McCreesh wrote: > On Mon, 12 Mar 2012 09:27:11 +0100 > Micha=C5=82 G=C3=B3rny wrote: > > 15-xml > >=20 > > and > >=20 > > - eapi: 15-yaml >=20 > You're carefully concocting your examples to make it look like it > should work. Or I am just printing the first thing that comes into my head. > If you go the XML route, though, the EAPI would either be in a DTD Like .../gentoo/eapi/15-xml.dtd ? That would match my regex as well, unless we allow dots in EAPI. > or as . No, definitely not. That's not the XML style. > Part of the point of all of this is that we shouldn't have to guess > what future EAPIs will look like. I'm just suggesting a way which will support a little more than bash-based solutions. We could also assume that if a file doesn't match the regexp at all, it's a unsupported EAPI. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/n5PyOtHbp0X/JzN1SXOfezU Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iJwEAQEIAAYFAk9dvTEACgkQfXuS5UK5QB2tzwQAgk3j89SyLA2Omdph34DrXYk6 mrbyD2z2KashdHUWOeGe07P10/Gq0nRz/1k4G1Q/22GBOTQS36FAttHJ3Dvmq6Jn R4onMEZ+wuMmKiwztc0VZPMvxsqYqHFkEuMnZWe5T0BpSqX5YrN7GV8+VIFGE7lT CoTBOP6L/RZCLtCcHws= =jiNa -----END PGP SIGNATURE----- --Sig_/n5PyOtHbp0X/JzN1SXOfezU--