From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MrXEU-0002MI-Cd for garchives@archives.gentoo.org; Sat, 26 Sep 2009 13:22:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4E4C6E0898; Sat, 26 Sep 2009 13:22:37 +0000 (UTC) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by pigeon.gentoo.org (Postfix) with ESMTP id 0C71AE0898 for ; Sat, 26 Sep 2009 13:22:36 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id d23so1089850fga.10 for ; Sat, 26 Sep 2009 06:22:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.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:message-id; bh=tNX0t0Wu0qY/XP2PBFfRgi7HGOioo2MH9JJPeXo/vqE=; b=wM4zJUTEHbOqiNCySrhmyZIChuDM/OMkRhS1Nczl0vTNFW4PGxOXLD/Y6c0fsGvacy vnDdHWuG2dokfgsy+6q4lHtd2pnuGYCX/2VcjILg8cPe8tmci8Zma3YwHeCmAJIdViNE 8stXX2ReRhB3FU8o/irYLFqUMXfjhhK0p5phc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=Jtw0qUPrC+cUFtkGwSIY6RRSXKcg/Pk1YphzvcuslZLT4G4Fl6yJUea9eR27R1LV5s KAUUBdP1o/uVmLmMc8tsqvg6539DTl/oXIdiZyKwilSKypUEWPhS2vfvC2IqBiB2dQDM rjEEsZXUu56rQU+9/UowT2459WJPaiqJoGyAU= Received: by 10.86.230.30 with SMTP id c30mr1803997fgh.68.1253971356509; Sat, 26 Sep 2009 06:22:36 -0700 (PDT) Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94]) by mx.google.com with ESMTPS id d4sm1616450fga.2.2009.09.26.06.22.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Sep 2009 06:22:35 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge? Date: Sat, 26 Sep 2009 15:22:30 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.31r4; KDE/4.3.1; x86_64; ; ) References: <4ABD68BD.7070806@wht.com.au> <20090926093213.0c70a08f@krikkit.digimed.co.uk> In-Reply-To: <20090926093213.0c70a08f@krikkit.digimed.co.uk> 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="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200909261522.30726.volkerarmin@googlemail.com> X-Archives-Salt: 20945078-2a72-42cc-9015-b303a30693a6 X-Archives-Hash: aab1b2b6fbcebea55079f2da4e1c3bcb On Samstag 26 September 2009, Neil Bothwick wrote: > On Sat, 26 Sep 2009 05:36:45 +0300, Nikos Chantziaras wrote: > > Furthermore, *after* "emerge -C oldPackageNoLongerNeeded", do: > > > > grep oldPackageNoLongerNeeded /var/lib/portage/world > > > > to see if it's still listed in the world file. If yes, remove all > > traces of it (you can simply edit this world file with a text editor, > > it's safe, but of course you might still want to make a backup of it.) > > emerge -C should remove it from the world file. If it does not, something > is broken that requires more than editing world. > > You can also check this with emaint -c world. > well sometimes an app appears more than once in world and after an removal instances remain - yes, it should not happen.