From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AE6861382C5 for ; Mon, 11 May 2020 16:13:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D8B9CE087E; Mon, 11 May 2020 16:13:25 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9E42DE0849 for ; Mon, 11 May 2020 16:13:25 +0000 (UTC) Message-ID: <88053e7bbb7e5505ce1c8f21bd06492c0fe4795d.camel@gentoo.org> Subject: Re: [gentoo-dev] [PATCH 0/1] remove EGO_VENDOR support from go-module.eclass From: David Seifert To: gentoo-dev@lists.gentoo.org Cc: William Hubbs Date: Mon, 11 May 2020 18:13:19 +0200 In-Reply-To: References: <20200510211645.19097-1-williamh@gentoo.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Archives-Salt: 32cbb4b7-688c-424c-83ed-bbece000c0b6 X-Archives-Hash: 5982a4218908aa6fe15f919924639ff3 On Mon, 2020-05-11 at 09:51 -0400, Mike Gilbert wrote: > On Sun, May 10, 2020 at 5:16 PM William Hubbs > wrote: > > All, > > > > now that go 1.14.2 is stable, I want to remove the EGO_VENDOR > > support from > > go-module.eclass. > > > > This was kept when the EGO_SUM support was added on 4 Mar, with a qa > > warning advising people to migrate their ebuilds to EGO_SUM. > > > > This patch makes migrating mandatory by forcing ebuilds to die if > > they > > have EGO_VENDOR set and are using go-module.eclass. > > > > Thoughts? > > It seems like you're being very lazy about this. At a minimum, you > should do the following: > > 1. Search for affected packages. > 2. Contact the maintainers, possibly via bug reports. > 3. Give them a some time to convert their packages. > 4. Mask any packages that do not get updated. > Wow, and python changing one line in its implementation details is breaking the world, whereas there's still a ton of users of EGO_VENDOR in the tree?