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 20620138BEA for ; Mon, 2 Mar 2015 14:26:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ACFAAE0959; Mon, 2 Mar 2015 14:26:36 +0000 (UTC) Received: from homiemail-a79.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) by pigeon.gentoo.org (Postfix) with ESMTP id 9A3B7E0909 for ; Mon, 2 Mar 2015 14:26:35 +0000 (UTC) Received: from homiemail-a79.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTP id 118E07D40CF for ; Mon, 2 Mar 2015 06:26:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=libertytrek.org; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= libertytrek.org; bh=Cc7nhT/cz2RekktzzXgG7pJ4FwU=; b=QDxpqzZ+4ztc yikkl4Q1LDvFRJd+u/78whwvLIewZNkm2SPGuxfqHyc/nJkThju9ueQ9Phyj3klt kZ4B18gp1iD2yvAOy2DWN6yvSDw7OjU2cxkBK4qMLya9I8pUsvzW7ZGSBcg1nAvT DGtkbbWxgZ4YhPXOeUFHzv0tDuamhs4= Received: from [192.168.1.110] (unknown [159.63.145.2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: tanstaafl@libertytrek.org) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTPSA id E59877D40C6 for ; Mon, 2 Mar 2015 06:26:34 -0800 (PST) Message-ID: <54F4731A.2010807@libertytrek.org> Date: Mon, 02 Mar 2015 09:26:34 -0500 From: Tanstaafl User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] perl-cleaner lerfovers References: <20150214123741.6f4d5b98@gentoo.local.lan> <54F46241.3080408@libertytrek.org> <20150302162521.6a677852@hobbit> In-Reply-To: <20150302162521.6a677852@hobbit> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: d653afdc-d3c0-4a8e-8268-eaa8017b844c X-Archives-Hash: a68abed28803e27ab9e54f499d97c7ad On 3/2/2015 9:25 AM, Alan McKinnon wrote: > On Mon, 02 Mar 2015 08:14:41 -0500 > Tanstaafl wrote: > >> On 2/14/2015 6:37 AM, bitlord wrote: >>> On Sat, 14 Feb 2015 13:13:25 Alexander Kapshuk wrote: >>>> 'perl-cleaner --all' generated the following output. >>>> >>>> * Finding left over modules and header >>>> >>>> * The following files remain. These were either installed by hand >>>> * or edited. This script cannot deal with them. >>>> >>>> /usr/lib/perl5/vendor_perl/5.16.3/XML/SAX/ParserDetails.ini >>>> /usr/lib/perl5/vendor_perl/5.18.2/XML/SAX/ParserDetails.ini >>>> /usr/lib/perl5/5.12.4/i686-linux/Encode/ConfigLocal.pm >>>> >>>> What's the recommended way to go about this? >> >>> As I understand this, it is safe to remove and that is what I do >>> when they appear on my system, if you don't have perl 5.16.3, >>> 5.18.2 or 5.12.4 ..., and updated/rebuild all perl modules with >>> perl-cleaner. >>> >>> I also used 'qfile /path/to/file' (from portage-utils) to check if >>> they belong to any installed package. (which is probably not needed, >>> per-cleaner knows about this?) >> >> I'm curious about this... >> >> After updating to 5.20, I got a similar message, but a lot more, and >> strangely, all of which (except the very last one) are in lib32 >> instead of lib64. >> >> So, to confirm, it is safe to remove these? >> >> If so, then I guess the obvious question is, *if* it really is safe to >> remove these, why doesn't portage just go ahead and do it >> automatically? >> >> Here is the list of files left over on mine: >> >> * The following files remain. These were either installed by hand >> * or edited. This script cannot deal with them. > > ^^^^^^^^^^^^^^^^^^^^ > > You missed this bit. The output clearly says that the script cannot > determine why the files are there or why they are different, therefore > it will NOT remove them. > > It's not portage giving you that output btw, it's perl-cleaner. It > works on the basis that it will only clean up files that a) portage > installed and b) that are still the same as when portage installed > them. If either case is not true, the script refuses to deal with it > and tells the human to make a decision. Oh, right, sorry, too much googling before my second cup of coffee... > In this specific case, all except two files come from emul-linux 32 bit > and they are all safe to delete (even the two except ones). But do note > I know this becuase I've been here before and figured it out, not > becuase of some magic portage flag. Thanks Alan... So... how would one know, for sure, if and when these are safe to delete? Would that be only if I know for sure that I did not manually install these myself or put them there (which I haven't and most likely wouldn't, but would remember if I did)?