From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Kixbl-0005KA-B5 for garchives@archives.gentoo.org; Thu, 25 Sep 2008 20:38:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 398EEE0229; Thu, 25 Sep 2008 20:38:40 +0000 (UTC) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by pigeon.gentoo.org (Postfix) with ESMTP id 0A98BE0229 for ; Thu, 25 Sep 2008 20:38:40 +0000 (UTC) Received: by gxk12 with SMTP id 12so8063919gxk.10 for ; Thu, 25 Sep 2008 13:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=Rr2WvzSCRWeTISJ5DF/czLHrGVmriHfMv7nkTzKmkek=; b=brf9X+de7IzJnehmQTofQFiO/YYmz5jC0xA0dk4nah9CxWpp2STv5yajE8XBTOSgXi V0RNrFt1JicHUk+TL0MZe6yUsD+PFD6iTDtFnaCVJqv+tM4BV3Ks+XfKYkH/ZQ/hV7Yv /1VaVsHLJDJc7l+m+Q/FAmH5UJyrLGw7F2OI8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=hv3Pe4rNwPzGhNYGp7YnlT48un+yjD2P+pZyB15fdwuSeG15Yn7b1yEUlL/JCddoWG h+2cykVX+PVWZlzzGPoBvZdDgV9JAQExSwbl4Tgz/Hqr82v+ji+8m5SIE27F8vpocvEn 3pBa/nu74cUrTZEQ+ZEN/GUmUDegYBxbig9hM= Received: by 10.65.219.20 with SMTP id w20mr412481qbq.43.1222375118535; Thu, 25 Sep 2008 13:38:38 -0700 (PDT) Received: from ?10.0.0.5? ( [41.243.218.139]) by mx.google.com with ESMTPS id k30sm1396000qba.4.2008.09.25.13.38.36 (version=SSLv3 cipher=RC4-MD5); Thu, 25 Sep 2008 13:38:37 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Question about difference between emerge --update world and emerge vigra Date: Thu, 25 Sep 2008 22:38:58 +0200 User-Agent: KMail/1.9.10 References: <384d42da0809242105k67b8e3feja376df615350a10c@mail.gmail.com> <6142e6140809250327o18816ed0r570f9adef20511ab@mail.gmail.com> In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809252238.59041.alan.mckinnon@gmail.com> X-Archives-Salt: 93a4e935-97f8-4d43-b385-05cb05a5e943 X-Archives-Hash: 38155233cbff3abe1f0c2d479dd767a1 On Thursday 25 September 2008 17:51:42 Hilco Wijbenga wrote: > On Thu, Sep 25, 2008 at 03:27, Daniel Pielmeier > > wrote: > > Also make sure you have a clean world file, which means if there is an > > entry which is already needed by something else it should normally be > > removed as this could cause problems. > > I can understand that if I have both package P and dependency D in > world, and I remove P then depclean will not remove D. I assume that's > not what you're talking about, though, as it's harmless and probably > intended (since I listed D in world). > > Moreover, I would think this is quite common. You might have > Java/Perl/Python/Ruby/* explicitely listed in world (because you write > programs/scripts) and several packages that are either > Java/Perl/Python/Ruby/* based or provide bindings. I *want* to be > explicit here as I don't want Java/Perl/Python/Ruby/* removed should I > remove those other packages. > > So what kind of problems are we talking about? Most probably the "problem" that arises is when a mere dep cannot be removed by --depclean anymore because it is in world. It is a problem because of the unnecessary clutter it creates. Also, sometimes deps come and go, and libs get split into two packages. Say you have libA which is a dep of some package Z. The dev sees that libA can benefit from USE flags in some way and this in turn benefits package Z. So libA gets split into libAa and libAb, both of which block the old libA. Package Z can install libAa or libAb or both depending on USE. If the user put the old libA in world (incorrectly), portage will not uninstall it to replace it with the new split libA. Instead it will display the blockers, which has to be resolved manually - and we all know how much mass hysteria and confusion blockers seem to cause amongst users... This of course is the exact opposite of what you describe above -- alan dot mckinnon at gmail dot com