From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16213 invoked from network); 6 May 2004 01:25:04 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 6 May 2004 01:25:04 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BLXdG-0005ku-Kz for arch-gentoo-portage-dev@lists.gentoo.org; Thu, 06 May 2004 01:25:02 +0000 Received: (qmail 335 invoked by uid 50004); 6 May 2004 01:25:01 +0000 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@lists.gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 5074 invoked from network); 6 May 2004 01:25:01 +0000 Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <29AF6280-9EFC-11D8-90CF-0003938E7E46@gentoo.org> Content-Transfer-Encoding: 7bit Cc: ppc@gentoo.org, Pieter Van den Abeele From: Pieter Van den Abeele Date: Thu, 6 May 2004 03:24:47 +0200 To: gentoo-portage-dev@lists.gentoo.org X-Mailer: Apple Mail (2.613) Subject: [gentoo-portage-dev] virtual evolution X-Archives-Salt: 3c4379fb-aeef-4e0f-9e61-ccd08b99d3af X-Archives-Hash: 8f6ce58b8df10dcb6b40958961255398 Hi, I have an annoying bug, caused by a portage deficiency that imho can be quite easily solved: Assume the virtual/jdk is satisfied by blackdown-jdk with version-1.3 (meaning: blackdown-jdk-1.3 is installed and provides virtual/jdk-1.3) The virtual/jdk default implementation is then changed from blackdown-jdk to ibm-jdk in the users profile. The user installs a package depending on virtual/jdk-1.4, ibm-jdk with version 1.4 gets installed. When the user runs emerge --update world, portage complains there is no 1.4 version of blackdown-jdk. To make emerge --update world work again, the user has to unmerge blackdown-jdk. If the user emerges blackdown-jdk again afterwards, emerge --update world still works. Shouldn't portage update the virtual provider every time an ebuild providing a virtual gets installed? Best regards, Pieter Van den Abeele -- gentoo-portage-dev@gentoo.org mailing list