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 1REsHB-0003XS-VZ for garchives@archives.gentoo.org; Sat, 15 Oct 2011 00:38:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0624921C039; Sat, 15 Oct 2011 00:38:46 +0000 (UTC) Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 385D521C026 for ; Sat, 15 Oct 2011 00:38:11 +0000 (UTC) Received: by vws19 with SMTP id 19so2326143vws.40 for ; Fri, 14 Oct 2011 17:38:11 -0700 (PDT) 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 Received: by 10.52.72.9 with SMTP id z9mr11100583vdu.70.1318639091564; Fri, 14 Oct 2011 17:38:11 -0700 (PDT) Sender: antarus@scriptkitty.com Received: by 10.52.171.131 with HTTP; Fri, 14 Oct 2011 17:38:11 -0700 (PDT) In-Reply-To: <4E98BCD9.5060204@gentoo.org> References: <4E8766F1.2020609@gentoo.org> <20111014193958.GA3465@localhost> <4E98A793.8050806@gentoo.org> <4E98B88F.3010206@gentoo.org> <4E98BCD9.5060204@gentoo.org> Date: Fri, 14 Oct 2011 17:38:11 -0700 X-Google-Sender-Auth: iHgYmhDeMUg67R4VYYUXv130x_0 Message-ID: Subject: Re: [gentoo-dev] python.eclass EAPI 4 support, this gets really annoying From: Alec Warner To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 472d58adb1f5897873765445802c7694 On Fri, Oct 14, 2011 at 3:51 PM, "Pawe=C5=82 Hajdan, Jr." wrote: > On 10/14/11 3:32 PM, Thomas Sachau wrote: >> What do you expect the council to do? > > Say it's OK to make python.eclass not die on EAPI-4. At least my use > case will not become broken by this. > >> Neither you nor the council can force anyone to do anything. > > Not really. It should always be possible to escalate painful issues like > this. I believe op's point is that there is no one to escalate the problem to; certainly the council members are not going to do the work themselves and we already have our best people on it. -A > >> The only thing you can do is to kindly ask about remaining issues and he= lping with solving them. And >> i am sure, that everyone would like to see some help to understand and i= mprove the python eclass. :-) > > Maybe we should start over. Seriously, I'm considering proposing some > lightweight eclass for python-dependent packages that *works* > >