From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] perl-cleaner lerfovers
Date: Mon, 2 Mar 2015 17:22:03 +0200 [thread overview]
Message-ID: <20150302172203.7f9b414e@hobbit> (raw)
In-Reply-To: <54F4731A.2010807@libertytrek.org>
On Mon, 02 Mar 2015 09:26:34 -0500
Tanstaafl <tanstaafl@libertytrek.org> wrote:
> > 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)?
I don't have a recipe for this or even a rule of thumb. I usually know
what the files are for (or can Google it) and decide on each case
individually.
For perl-cleaner output, the perl version of the old install is in the
pathname, so I check if the corresponding file for the new perl version
is already installed, that tells me the old one is safe to delete. On a
64bit system, I know the 32bit files come from emul-linux, so I can
delete those too on the same basis.
For everything else from perl-cleaner, I have to figure out why I
changed the file myself and make sure the same change is present in the
new version.
It gets more complicated if you use cpan (stuff can get changed behind
the scenes). So the best approach is always to understand what the
various tools do and deal with it on that basis.
Alan
next prev parent reply other threads:[~2015-03-02 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 11:13 [gentoo-user] perl-cleaner lerfovers Alexander Kapshuk
2015-02-14 11:37 ` bitlord
2015-02-14 11:48 ` Alexander Kapshuk
2015-02-14 12:12 ` Mick
2015-02-14 12:19 ` Alexander Kapshuk
2015-02-14 12:39 ` Mick
2015-02-14 12:46 ` Alexander Kapshuk
2015-02-14 14:06 ` Peter Humphrey
2015-02-15 22:52 ` Walter Dnes
2015-02-16 16:35 ` Alexander Kapshuk
2015-02-16 16:40 ` Mick
2015-02-16 21:25 ` Neil Bothwick
2015-02-17 16:15 ` Alexander Kapshuk
2015-03-02 13:14 ` Tanstaafl
2015-03-02 14:25 ` Alan McKinnon
2015-03-02 14:26 ` Tanstaafl
2015-03-02 15:22 ` Alan McKinnon [this message]
2015-02-14 15:24 ` Alan McKinnon
2015-02-14 15:42 ` Alexander Kapshuk
2015-02-14 16:04 ` Alan McKinnon
2015-02-14 16:09 ` Alexander Kapshuk
2015-02-14 17:08 ` Andreas K. Huettel
2015-02-14 17:16 ` Alexander Kapshuk
2015-02-14 19:19 ` [gentoo-user] perl-cleaner leftovers Thanasis
2015-02-14 20:07 ` Alexander Kapshuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150302172203.7f9b414e@hobbit \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox