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 11AAF139694 for ; Mon, 10 Apr 2017 21:17:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0194B21C170; Mon, 10 Apr 2017 21:17:37 +0000 (UTC) Received: from forward5j.cmail.yandex.net (forward5j.cmail.yandex.net [5.255.227.23]) (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 9C5E621C090 for ; Mon, 10 Apr 2017 21:17:36 +0000 (UTC) Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [IPv6:2a02:6b8:0:f05::115]) by forward5j.cmail.yandex.net (Yandex) with ESMTP id 58B6920C04 for ; Tue, 11 Apr 2017 00:17:33 +0300 (MSK) Received: from smtp1h.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id 315528C0CE3 for ; Tue, 11 Apr 2017 00:17:32 +0300 (MSK) Received: by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id oqzhFLgNkJ-HV40Nm8p; Tue, 11 Apr 2017 00:17:31 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) X-Yandex-Suid-Status: 1 0 From: "Vadim A. Misbakh-Soloviov" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Reverse use of Python/Ruby versions Date: Tue, 11 Apr 2017 04:17:31 +0700 Message-ID: <2963055.WlKhBU30F8@note> In-Reply-To: References: <5950999.Gx5BNhHzAl@note> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 7204835d-7726-4a17-bf06-c4253150d485 X-Archives-Hash: 4343021fb884214a20e63b4fdeaccb5d Also, > Its an update issue. You set a target to say Ruby 24. But something > wants Ruby23. It could be it only builds with ruby23. Or more than > likely no one has gotten around to adding it to the package. Since for > every new version. EVERY ebuild must be touched. As I said above, this only happens if package manintainer is a slacker and a package wasn't touched for years. Chances that it will work with new ruby is... about 0%. Why should you auto- add modern ruby targets for it then? Instead, you should blame package (that causes regression) maintainer and/or take maintenance in your hands (if you need that package), or just drop it from your system (if not). // Although, it is another question to discuss: Most of time in such situations (with ruby crap mess, lol) Portage is unable to tell which exact package is guilty in all that crap (even with --verbose- conflicts --backtrack=100500 and so on) and you need to mask old rubys and re- run world-upgrade to catch the one who fails because of mask. I agree that it is not expected portage bahaviour, but I have not done deep research to write detailed report and suggest a solutions for this problem, abd just reporting it was useless, since, predictably, nobody cares (everybody ok with this). That ^ is the point to discuss. But I disagree that '>=foo-1 <=foo2' stuff should be used instead of targets.