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 1N1RMZ-0004Bk-NR for garchives@archives.gentoo.org; Fri, 23 Oct 2009 21:07:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8547FE09EB; Fri, 23 Oct 2009 21:07:54 +0000 (UTC) Received: from mail-qy0-f191.google.com (mail-qy0-f191.google.com [209.85.221.191]) by pigeon.gentoo.org (Postfix) with ESMTP id 68FC4E09EB for ; Fri, 23 Oct 2009 21:07:54 +0000 (UTC) Received: by qyk29 with SMTP id 29so6311949qyk.32 for ; Fri, 23 Oct 2009 14:07:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=phz7IWWPmN5n7Fnfbn4GIdxuSGWsqkQmjnOlBeIwBmE=; b=TIzRN1jP5NJQb6tztzouGsQlmvExB2J98QZSYzZ2f2SSf7OZM/DhKxUd3ozs5bexgN hpjNGA3ctWknjhd6ciCzKg4UI1I5ROWYVrNvxtr3s+1vzAl4slxABMXnUfSXBHGAQvSf OaCTx89QYuv/fNoydCReuwEttyu1Sv0WqvOs4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=RFm7PdmlY1DA2yDbp4fQjnU0zSIX4nu+1lSlLMYXORGswZ+MvSzpFhEIZDJvy33m1/ 8dOH/VybR3g2TMqmeTukDHNIgae5KZwEEX49u7iBCnNQF30MzSllQ6iticJmJWvu3U8J 3AZFb0tfdvJ2jOynyg7Ktdbmu4fTZFIlz4k6s= Received: by 10.224.115.152 with SMTP id i24mr5753988qaq.276.1256332074140; Fri, 23 Oct 2009 14:07:54 -0700 (PDT) Received: from smtp.gmail.com (173-13-149-190-sfba.hfc.comcastbusiness.net [173.13.149.190]) by mx.google.com with ESMTPS id 2sm9042386qwi.2.2009.10.23.14.07.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 23 Oct 2009 14:07:53 -0700 (PDT) Received: by smtp.gmail.com (sSMTP sendmail emulation); Fri, 23 Oct 2009 14:04:25 -0700 Date: Fri, 23 Oct 2009 14:04:25 -0700 From: Brian Harring To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] eapi files and profiles Message-ID: <20091023210425.GA7171@hrair> References: <4AE1683B.7090106@gentoo.org> 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-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <4AE1683B.7090106@gentoo.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: c7733573-f3d8-4270-923a-9442efa03f90 X-Archives-Hash: e323c52502599ee331cb97d353b259fe --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 23, 2009 at 11:24:27AM +0300, Samuli Suominen wrote: > So I was told Council needs to approve inheritance of eapi files from > parent profiles? >=20 > I'm not sure why, because we shouldn't have any files in default/linux/ > which was decided long ago when the new profiles was introduced... >=20 > gentoo-x86/profiles/default/linux $ find ./ -name eapi | wc -l > 63 >=20 > That's 63 duplicated files. We should only have one releases/10.0/eapi > file, and others wouldn't be required as it would cover all the 10.0 > profiles. >=20 > See, http://bugs.gentoo.org/288320 >=20 > Can we get a decision on this soon, so we can drop the duplication for > 10.1 (or whatever the name for next profile set will be called) ? This is going to break compatibility for pkgcore at least- we limit=20 what forms of atoms are allowed dependant on the eapi of that profile=20 node. I'd hope paludis does the same- I know portage doesn't however. Further... the more I think about this, the more I'm inclined to think=20 this will blow someones foot off. If the eapi is inherited from the=20 parent, what happens when the parent switches to an EAPI that changes=20 the atom parsing rules? Specifically, *restricts* the atom parsing=20 rules? Say that we got rid of the ~ operator w/in EAPI4. '~' is completely=20 valid in the default EAPI=3D0; if the parent profile switches to EAPI4,=20 it suddenly breaks parsing of any defaulted EAPI that used revision=20 matching. So... inheritance sucks. It gets worse when you have user=20 configuration (custom profiles) inheriting from gentoo-x86 provided=20 profiles- I'd expect user config to use things that are more cutting=20 edge. Alternative approach- the default EAPI currently is 0, and isn't=20 overridable. Add a file into the base of the profile directory that=20 specifies the default EAPI. Via that, you can do your file optimizations- if the majority of=20 profile nodes are eapi=3D2, then you set the default to 2 and update the=20 nodes that were reliant on the previous default. Note this still requires having this change sit in the tree for a=20 while for compatibilty reasons- but it is a good idea regardless to=20 avoid requiring EAPI to be specified for every single profile node=20 when we've hit EAPI=3D7.... ~harring --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkriGlkACgkQsiLx3HvNzgc/rgCgyJxbXbGVlFO4ss9t3rpczlxp FGkAoLoW24waVoZefpILjNS+dzEHvPZD =DlHi -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx--