From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] broken libraries but library-linking is consistent ;-)
Date: Wed, 14 Jun 2006 14:41:26 +0100 [thread overview]
Message-ID: <20060614144126.1498c53a@hactar.digimed.co.uk> (raw)
In-Reply-To: <41038.141.38.43.231.1150289519.squirrel@ulm114.server4you.de>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Wed, 14 Jun 2006 14:51:59 +0200 (CEST), Norman Rieß wrote:
> But why wasn´t this deleted by a emerge --depclean world or the unmerge
> in the update-process of that packages.
Because the files' datestamps and/or checksums had changed since they
were installed. Portage won't remove a file that has been changed since
its emerge. The most likely cause is that you ran fix_libtool_files.sh.
If you run the files through equery belongs, I expect you will find that
no package owns them, so they can be safely removed.
> Who knows what other garbage-files live on my system and someday try to
> overrule my control and start to think for themselves.
These files are owned by nothing and used by nothing. all they do is take
up a small amount of disk space. They won't start to think for themselves
unless you have skynet in your USE flags.
--
Neil Bothwick
Therapy is expensive, popping bubble wrap is cheap! You choose.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-14 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 11:52 [gentoo-user] broken libraries but library-linking is consistent ;-) Norman Rieß
2006-06-14 12:28 ` Benno Schulenberg
2006-06-14 12:51 ` Norman Rieß
2006-06-14 13:41 ` Neil Bothwick [this message]
2006-06-14 15:25 ` Norman Rieß
2006-06-14 16:09 ` Neil Bothwick
2006-06-14 16:39 ` Richard Fish
2006-06-14 17:11 ` Neil Bothwick
2006-06-14 15:27 ` Rumen Yotov
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=20060614144126.1498c53a@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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