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 D1D0D1382C5 for ; Sun, 25 Mar 2018 10:13:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 27DE0E07ED; Sun, 25 Mar 2018 10:13:34 +0000 (UTC) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (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 AE38DE07AE for ; Sun, 25 Mar 2018 10:13:33 +0000 (UTC) Received: from mxback19j.mail.yandex.net (mxback19j.mail.yandex.net [IPv6:2a02:6b8:0:1619::95]) by forward100j.mail.yandex.net (Yandex) with ESMTP id E0B5A5D828E5 for ; Sun, 25 Mar 2018 13:13:30 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback19j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id LgyAlXzU1K-DTB4dWUs; Sun, 25 Mar 2018 13:13:30 +0300 Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id cybJScnhk3-DTcWFK06; Sun, 25 Mar 2018 13:13:29 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) From: "Vadim A. Misbakh-Soloviov" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] New Portage fork: sys-apps/portage-mgorny Date: Sun, 25 Mar 2018 17:13:28 +0700 Message-ID: <22057579.quYvPxvz6Q@note> In-Reply-To: References: <1521745426.836.25.camel@gentoo.org> <1521756383.23424.0.camel@gentoo.org> 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: f0180425-4217-4594-b14c-4a8214903b44 X-Archives-Hash: aedd0a63acd6fbaaeb1f39b960d5b033 Well, in *my* opinion, in turn, having possibility to {R,}DEPEND on package from exact repo is much and much more needed functionality. Say, I have pkg2 in my repo, that depends on pkg1, which is in my repo too. Then, I (or user) add other repo having pkg1 too. Or, say, gentoo maintainers bump pkg1 to a newer version (while I'm slacking a bit). And my pkg1 is a bit different from gentoo's (let it be patchset, or, say, lua.eclass support for lua overlay). So, that changes results in random unexpected behaviour as blocks, runtime breakage and so on. And renaming all the packages to not collide with gentoo/other repos naming is, well, not an option, I think. Or, another example: I making pkg4 in my repo1, which depends on pkg3 from repo2 (where I 100% sure it fits all the requirements and the patchsets), while pkg3 in ::gentoo doesn't (and it can even have a bug about that opened for a century already). Currently, it is no way to say "only dep-pkg from that exact repo is 100% works as expected", so there is still the chance, that someday pkg4 would fail to build because suddenly pkg3 was reinstalled from another "incompatible" repo... And, honestly, current ways to resolve that issue (adding dummy-useflags, copy_here&rename, and so on) looks as very dirty hacks.