From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D47211391DB for ; Sat, 26 Jul 2014 08:06:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F227AE0D01; Sat, 26 Jul 2014 08:05:59 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 00294E0CA6 for ; Sat, 26 Jul 2014 08:05:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id BED8C3400B8 for ; Sat, 26 Jul 2014 08:05:57 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -1.504 X-Spam-Level: X-Spam-Status: No, score=-1.504 tagged_above=-999 required=5.5 tests=[AWL=-0.801, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOvSlU83kDTi for ; Sat, 26 Jul 2014 08:05:52 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id C1FAD34002D for ; Sat, 26 Jul 2014 08:05:51 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XAwzA-0001LP-Hk for gentoo-dev@gentoo.org; Sat, 26 Jul 2014 10:05:44 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Jul 2014 10:05:44 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Jul 2014 10:05:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: RFC: USE flags in virtuals, to allow a specific provider to be determined Date: Sat, 26 Jul 2014 08:05:32 +0000 (UTC) Message-ID: References: <53D2A6C8.9060900@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-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT d447f7c /m/p/portage/src/egit-src/pan2) X-Archives-Salt: fcf71edf-5db3-444c-b8e8-1c6b3bc6d029 X-Archives-Hash: a451c9a64378b28fc7674f993c56d5fb Ian Stakenvicius posted on Fri, 25 Jul 2014 14:49:44 -0400 as excerpted: > Hey all.. So, putting aside for now how much of a mess this would be to > implement in the virtuals' ebuilds themselves, what do people think of > changing the virtuals so that they contain an entry in IUSE for each > provider that can satisfy it? > > The idea here is that the package satisfying a virtual could be > optionally explicitly-chosen through package.use (or USE= in make.conf, > perhaps) instead of having an entry in @world, that way if nothing > depends on the virtual then it and the provider can be - --depclean'ed > from the system. The idea is specifically NOT to have rdeps depend on > these flags, that would undermine the whole purpose of the virtual; it > would just be for end-users to set if they so chose. > > This may also help with getting portage to peg a virtual's provider to a > specific package instead of constantly trying to switch from one to > another, ie, how systemd kept getting pulled in, in relation to the > upower virtual. What about handling each such virtual_USE as a USE_EXPAND? VIRTUAL_* as reserved-namespace USE_EXPAND would give us full backward compatibility along with an immediately identifiable namespace and virtually (heh) no possibility of confusion with other configuration. Continuing with the earlier virtual/krb5 example, we'd have VIRTUAL_KRB5, with possible settings in make.conf of: VIRTUAL_KRB5=mit-krb5 VIRTUAL_KRB5=heimdal Virtually no possibility of confusion with normal USE flags, and the matching virtual would be immediately identifiable, so no possibility of getting confused on what it applies to, either. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman