From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 18171138010 for ; Thu, 30 Aug 2012 11:00:57 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B4E05E062B; Thu, 30 Aug 2012 11:00:28 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 692C7E058F for ; Thu, 30 Aug 2012 10:59:13 +0000 (UTC) Received: from [192.168.4.5] (blfd-4d08f56c.pool.mediaWays.net [77.8.245.108]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hasufell) by smtp.gentoo.org (Postfix) with ESMTPSA id B4FEE33C721 for ; Thu, 30 Aug 2012 10:59:11 +0000 (UTC) Message-ID: <503F477B.2050507@gentoo.org> Date: Thu, 30 Aug 2012 12:59:07 +0200 From: hasufell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120801 Thunderbird/10.0.6 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] EAPI usage References: <1650487.RNHkTcOSMI@elia> In-Reply-To: <1650487.RNHkTcOSMI@elia> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: fb4c0f7d-7e57-4d6d-b11d-b4d9ac8dcc72 X-Archives-Hash: 68c7d39d1fe019f08a9ef4ab45e80a70 On 08/30/2012 12:28 PM, Johannes Huber wrote: > Hello gentoo devs, > > From last council meeting summary: > [snip] >> Open floor >> ========== >> scarabeus suggested the change "dev should use latest eapi when bumping" >> to "dev must use latest eapi when bumping if not forbidden by eclasses". >> He was asked to bring it up on the mailing lists, to get a better >> definition of when what EAPI should be used. > [/snip] > > I raised the issue through scarabeus, as in my opinion there is no reason to > not use latest EAPI. So please discuss. > > Greetings, Could you elaborate what the reasons FOR it are (not that I don't know any, but you brought it up) since this will add work for every developer to check a) how the behavior of the new EAPI impacts the current ebuild and b) how the behvaior of inherited eclasses change depending on EAPI.