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 13B28139694 for ; Mon, 10 Apr 2017 00:37:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 841CE21C07E; Mon, 10 Apr 2017 00:37:13 +0000 (UTC) Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (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 1BE2921C054 for ; Mon, 10 Apr 2017 00:37:12 +0000 (UTC) Received: by mail-wr0-x22c.google.com with SMTP id c55so64997054wrc.3 for ; Sun, 09 Apr 2017 17:37:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=wDczakkVBH6Dwf6fDOA6dDTBV0HxbNLDCSI5W9tL9TU=; b=REBd4D3IQI2t1DHYWQDrXsmqJAQ5+/hKlyBf+J7w2ZPzViE0ZKU+yMIQtD1niuRPJk 7tQqZInjMhE3F5LUGLfRpP5IDqxxHOr7c02b5lh9hObHKROpy/+lpMyzJ6sKJpCUrJ/C ju91QFkWwfWdZnFvgVthwNshxiwZVZeS7zayoDwl72OwxtvppCrjHoOyF9QMGyG2PybR fPsUFv5NbGZGopCGNZ4FtM4WaV3QY1f7PCIhfKQZi/4A0xSs9NHxi510ltBveh8NJR1l dZS1BimB7AJAdk40+ymneKBfy0z6DuZHZg2vudjJd7hNO3qWudlFIccnQDxRoQpYqKCK ma+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=wDczakkVBH6Dwf6fDOA6dDTBV0HxbNLDCSI5W9tL9TU=; b=QvJ0RsoaXYXVNzv07vXYpV3FJxzM53mzSLvC3TqjlDofhBVN3+iAzOGrEBN0hO0FFJ SZW5ShiVqJbyS5WfrVdbuyznxe8mqvdF9S7yQSNDRtZZ3OJmlmgec1s9xvwrp016HFR0 NSEfYHfa4//xil+fgje5/Naf0jXDfKVFeShyKq1mgz0AMmDSqSD1leQsgvukwlevkbTA IelKFn8GR2m9BnTVJFGTq3LwoXbhRwIdR86RizyfYoEs0agYAkpOxp1vcjym7mIHPgI9 NgTx3PC9hoqods+ailq3w1MkU54Mbw0/HcQW8cy6H3v+IkKdMguNXWOuonoB1Tc/Qslk KdpQ== X-Gm-Message-State: AFeK/H1ECoGX/EjETwr3E5NlMBw8iYbDgIxk6oVBXIKlROQRXcWpIkJ5mKBPN/yskCSvNw== X-Received: by 10.223.145.199 with SMTP id 65mr40584679wri.182.1491784631319; Sun, 09 Apr 2017 17:37:11 -0700 (PDT) Received: from [192.168.1.128] (net-5-89-218-40.cust.vodafonedsl.it. [5.89.218.40]) by smtp.gmail.com with ESMTPSA id l141sm8103474wma.32.2017.04.09.17.37.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Apr 2017 17:37:10 -0700 (PDT) Subject: Re: [gentoo-dev] Reverse use of Python/Ruby versions To: gentoo-dev@lists.gentoo.org References: <20170409152002.550f3b4d.dolsen@gentoo.org> <0cf71d18-64f3-821b-e481-9889f5eb1872@gentoo.org> From: Francesco Riosa Message-ID: <7a758d44-160a-7072-ff44-237f3a971940@gmail.com> Date: Mon, 10 Apr 2017 02:37:09 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 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 In-Reply-To: <0cf71d18-64f3-821b-e481-9889f5eb1872@gentoo.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 5aaefc34-fe91-4c3b-a094-460c99d75dd8 X-Archives-Hash: 535d1bb58e6b62f9b1bf1052b2f62455 On 10/04/2017 01:59, Michael Orlitzky wrote: > On 04/09/2017 07:15 PM, William L. Thomson Jr. wrote: >> >> If the package failed, all that would need to be done kinda like now is >> a given variable modified in the ebuild. Just marking what ever it did >> not work with. As mentioned that could be done via my >> ebuild-batcher[1], though same functionality is easily replicated. >> > > How do you plan to test a thousand packages against the new version of > python, and then revision/stabilize all of the broken ones > immediately? Or is the plan to just break everyone's systems, and ask > them to report bugs for the things that stopped working? python 3.5.0 was released on 2015-09-13 and is still marked unstable and until recently was unusable because there were too many missing packages marked ready for it, stabilization isn't that faster right now. Most of the breakage would be caught when recompiling (bytecode) of a package stable or not and even when not caught it would trigger only eselecting an unstable dev-lang/python if testing all python packages is required to stabilize dev-lang/python (which is kinda the current situation). Python is slotted, that would also help a lot at keeping the breakage unobtrusive * * Provided portage is never broken by a dev-lang/python update, but that's easy to test. > > I think what you will actually get as a result is that nobody will > ever add a new version of python to the tree, because you've just made > it a huge ordeal to do so. > I do respectfully disagree with this sentence.