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 1NL4Br-0005ZD-M4 for garchives@archives.gentoo.org; Thu, 17 Dec 2009 00:26:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4FDA0E0D35 for ; Thu, 17 Dec 2009 00:25:59 +0000 (UTC) Received: from jolexa.net (jolexa.net [69.164.197.24]) by pigeon.gentoo.org (Postfix) with ESMTP id 3B2BBE0BD9 for ; Wed, 16 Dec 2009 22:55:06 +0000 (UTC) Received: by jolexa.net (Postfix, from userid 101) id EC68F5BA55; Wed, 16 Dec 2009 22:55:05 +0000 (UTC) To: Subject: Re: [gentoo-dev] [RFC] =?UTF-8?Q?EAPI=3D=7B=33=2C=34=7D=20offset-prefix?= =?UTF-8?Q?=20semantics=20mandatory=3F?= 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 Date: Wed, 16 Dec 2009 22:55:05 +0000 From: Jeremy Olexa In-Reply-To: <20091215185944.GA9600@gentoo.org> References: <20091215185944.GA9600@gentoo.org> Message-ID: <312bc88834c8c0efb776b307cdb8ee7e@jolexa.net> X-Sender: darkside@gentoo.org User-Agent: RoundCube Webmail/0.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: bae35f78-2eec-406d-8b26-44d53c14e77f X-Archives-Hash: c87dfbb5f0487d37ef15789c9f271ec7 On Tue, 15 Dec 2009 19:59:44 +0100, Fabian Groffen wrote: > With the current route where EAPI=3D3 will simply be EAPI=3D2 + > offset-prefix support, and EAPI=3D4 will be EAPI=3D3 + some other stuff= , the > following question arose: >=20 > Should an ebuild using an EAPI that has offset-prefix support make th= e > use of that support mandatory or optional? As a Gentoo Linux developer, I certainly wouldn't want to say that my EAPI-3+ ebuilds are guaranteed to work on Gentoo Prefix platforms without testing(keywording) it. As a Gentoo Prefix user, I certainly wouldn't want devs that don't know how to test an ebuild to work on Gentoo Prefix to say that it works. As a Gentoo Prefix developer, I certainly don't want to fix bugs by peopl= e that don't know how test on (or have access to) Gentoo Prefix. In the end, every Gentoo Prefix arch needs a specific keyword anyway. Unless that changes, I can't say that I see many benefits to making offset-prefix support mandatory in EAPI-3. OTOH, if it is mandatory and I screw it up for Gentoo Prefix platforms, no one will know until it gets keyworded (and hence tested). -Jeremy > In other words, one can perfectly fine write an ebuild EAPI=3D3 that wi= ll > not work in an offset-prefix install, due to improper absence of EPREFIX, > ED and EROOT. Should we allow this formally, or not? >=20 > Why is this a problem? Simply because it can be done, but more because > EAPI=3D4 will introduce features a developer would like to use/rely on, > while she/he does not want, or is not able to write the ebuild in a > Prefix conforming way. >=20 > The pros for forcing ebuilds to be offset-prefix aware are: > - an ebuild having EAPI >=3D 3 (as it looks now) is supposed to work > for Prefix users > - hence also obviously is (supposed to be) checked for Prefix > - repoman might be able to check for obvious mistakes regarding > offset-prefix installations >=20 > The cons: > - all developers need to be aware of how Prefix works, and be able to > write ebuilds for it (I can post all the answers to the Prefix quiz) > - basically requires a Prefix to be setup to test > - it will stop developers to some degree to use higher EAPIs in the > worst case >=20 > The pros for allowing ebuilds that have an offset-prefix aware EAPI to > ignore the offset-prefix are: > - easy drop-in replacement for devs, basically the contra of all the > cons of the previous approach. >=20 > The cons: > - not immediately clear which ebuild is offset-prefix aware (could look > at Prefix keywords) > - needs proper rules; an ebuild that has offset-prefix support may not > have this support removed again (breaks Prefix users, how to enforce?= ) > - ebuilds may get offset-prefix support at a later stage, which may not > entirely be understood/noticed by (their maintaining) devs >=20 > Please voice your opinion and share your insights, if any.