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 1M5LFK-0005qv-0m for garchives@archives.gentoo.org; Sat, 16 May 2009 14:52:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE412E03A1; Sat, 16 May 2009 14:52:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 8BB92E03A1 for ; Sat, 16 May 2009 14:52:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 2CE58660E6 for ; Sat, 16 May 2009 14:52:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -0.873 X-Spam-Level: X-Spam-Status: No, score=-0.873 required=5.5 tests=[AWL=0.659, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ltaX20feHr6t for ; Sat, 16 May 2009 14:52:10 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 7043765F30 for ; Sat, 16 May 2009 14:52:08 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1M5LEw-0000a5-E6 for gentoo-dev@gentoo.org; Sat, 16 May 2009 14:51:54 +0000 Received: from 82.152.254.57 ([82.152.254.57]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 May 2009 14:51:54 +0000 Received: from slong by 82.152.254.57 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 May 2009 14:51:54 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Steven J Long Subject: [gentoo-dev] Re: The fallacies of GLEP55 Date: Sat, 16 May 2009 15:50:39 +0100 Organization: Friendly-Coders Message-ID: <5981172.Hf5BpBib5L@news.friendly-coders.info> References: <200905142006.51998.patrick@gentoo.org> <4A0C790A.1050209@gentoo.org> <20090514231623.409c8eb7@gentoo.org> <20090514214909.GA23080@linux1> <20090514225337.34df7dac@snowcone> <20090515194329.GA16382@linux1> <20090515204905.54aa6a5c@snowmobile> <20090516092710.GA3221@eric.schwarzvogel.de> <20090516151216.15efc792@snowmobile> 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: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 82.152.254.57 Sender: news X-Archives-Salt: c634ea55-9647-4627-b894-f0915f99af09 X-Archives-Hash: 8af758cdcd995b71aa0d396b5e845ac0 Ciaran McCreesh wrote: > On Sat, 16 May 2009 11:27:10 +0200 > Tobias Klausmann wrote: >> Change the spec, then. > > If we change the spec, we can't do anything with the change until we're > absolutely sure that everyone's updated both their ebuilds and their > package manager for it. > Isn't that what the EAPI process is for? The "support every overlay and old version of portage known to Gentoo" is a "straw man" as one hears so much of. GLEP-55 makes explicit mention of waiting for 2008.0 to ship, and Gentoo is ultimately only responsible for the software it ships, including sunrise. Since this is Gentoo, ofc, users will be kept in the loop, and upgrade paths will be provided. It's about the users, or it used to be. (As is the GPL.) >> Actually, I personally would prefer taking it out of the >> parsed-by-bash part entirely. Add it as a shebang-like line at >> the top: >> >> #EAPI-1 >> >> as the first or second line. Allowing it on the second line >> allows you to later bolt on a true shebang-line if you should so >> desire. Only having to look at the first two lines makes finding >> it out easier (note that I don't call that parsing on purpose). > Restricting (via repoman or equivalent) to first non-comment line means we can use existing ebuilds with a minor edit, which can be automated as part of repoman, with a warning if not -q etc, and makes it easier to find, and to scan for. (I agree, it's not parsing.) > Would mean we'd have to change every existing ebuild everywhere. > >> I was under the impression that it's illegal to change/set the >> EAPI after using inherit. > > Nope. It's considered by some to be a QA violation, but EAPI's rules > are the same as the rules for any other metadata variable. > So refine the spec; that's what the discussion is supposed to lead to, remember? -- #friendly-coders -- We're friendly but we're not /that/ friendly ;-)