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 75BF9139694 for ; Sun, 9 Apr 2017 22:35:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7362D21C07D; Sun, 9 Apr 2017 22:35:07 +0000 (UTC) Received: from mail1.obsidian-studios.com (mail.obsidian-studios.com [173.230.135.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1B2E8E0CD8 for ; Sun, 9 Apr 2017 22:35:06 +0000 (UTC) Received: (qmail 25133 invoked from network); 9 Apr 2017 22:35:05 -0000 Received: from unknown (HELO assp1.obsidian-studios.com) (wlt-ml@::ffff:127.0.0.1) by ::ffff:127.0.0.1 with ESMTPA; 9 Apr 2017 22:35:05 -0000 X-Assp-Version: 2.5.5(16366) on assp1.obsidian-studios.com X-Assp-ID: assp1.obsidian-studios.com m1-77305-12065 X-Assp-Session: 32A14538D20 (mail 1) X-Assp-Envelope-From: wlt-ml@o-sinc.com X-Assp-Intended-For: gentoo-dev@lists.gentoo.org X-Assp-Server-TLS: yes Received: from unknown ([fdbe:bad:a55:0:1::211] helo=localhost) by assp1.obsidian-studios.com with SMTPSA(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.5.5); 9 Apr 2017 18:35:05 -0400 Date: Sun, 9 Apr 2017 18:34:55 -0400 From: "William L. Thomson Jr." To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Reverse use of Python/Ruby versions Message-ID: In-Reply-To: <1c3c5bd1-a697-25fd-4851-2f850b2ba06a@gentoo.org> References: <1c3c5bd1-a697-25fd-4851-2f850b2ba06a@gentoo.org> Organization: Obsidian-Studios, Inc. X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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; boundary="Sig_/5B7Sy+m=znq2RqfLo9vPVmk"; protocol="application/pgp-signature" X-Archives-Salt: d82e94d4-d95d-464c-a0e5-30983704f8e7 X-Archives-Hash: ac75f2d6c4362f9ed5c15104f8869738 --Sig_/5B7Sy+m=znq2RqfLo9vPVmk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 9 Apr 2017 17:52:44 -0400 Michael Orlitzky wrote: > On 04/09/2017 12:15 PM, William L. Thomson Jr. wrote: > > Not sure if this is practical, it may be less work if the use of > > Python and Ruby versions ( maybe others ) is reversed. Rather than > > adding all the versions that the ebuild supports. What if it only > > included versions it did not support? =20 >=20 > Even if this would work better, it would require retraining all=20 > developers, completely rewriting several eclasses, tons of=20 > documentation, and a few thousand ebuilds. There could be things done to ease any transition. Regarding python, the first of which could be to ignore any targets beyond say 2.7 and just starting enabling support. That would mostly leave just effected packages, ones that break with some 3.x version but not with another. As for modifying a few thousand ebuilds; 1, That is already the case now. If a new python or ruby version comes out. All those ebuilds have to modified to support the new target. That argument isn't really valid. 2. As for the actual changes that can be done pragmatically if just swapping out the TARGETS variable. Or even if more advanced requiring changing lines. If its the same change to all. I have a script, ebuild-batcher[1], that can safely make any change to a massive number of ebuilds. I have used it a few times on hundreds of ebuilds. It can easily handle thousands. > No one's going to jump on that bandwagon without a proof-of-concept > that works much better than what we have now. Anyone who has worked with a Gentoo system long enough that has Python and/or Ruby has experienced this. You end up having multiple TARGETS and are constantly messing with those variables adding new ones, removing old, etc. It creates a considerable amount of work. I have been fighting over ruby23 that I cannot seem to avoid. Despite having had ruby24 for I think at least a week or more. My build server stopped due to needing ruby23. I have been fighting with stuff around that. More than likely anything bound to ruby23 target works with ruby24. Its mostly how the system is designed. I could be wrong in that case and something require ruby23, that does not with ruby24. However most those packages do not have a ruby24 target, so its hard to say if its negated or just not enabled yet. Being a new version, all have to be modified for such. 1. https://github.com/Obsidian-StudiosInc/ebuild-batcher --=20 William L. Thomson Jr. --Sig_/5B7Sy+m=znq2RqfLo9vPVmk Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTEeldqZjmVut8bVHJNcbKkg6ozUAUCWOq3DwAKCRBNcbKkg6oz UE5SAJ9v+kN/snHIYp7PkD792yBTIQynTwCdE9GaWMBoDSePcjiZ4Po5KZfe070= =dbIc -----END PGP SIGNATURE----- --Sig_/5B7Sy+m=znq2RqfLo9vPVmk--