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 1S74Jc-0007lH-Q2 for garchives@archives.gentoo.org; Mon, 12 Mar 2012 12:25:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 80771E0BFA; Mon, 12 Mar 2012 12:25:00 +0000 (UTC) Received: from mx1.hadt.biz (boss.hadt.biz [78.47.36.129]) by pigeon.gentoo.org (Postfix) with ESMTP id 2B7E0E0C1A for ; Mon, 12 Mar 2012 12:23:23 +0000 (UTC) Received: from [192.168.255.100] (p5B341671.dip.t-dialin.net [91.52.22.113]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.hadt.biz (Postfix) with ESMTPSA id 141E214C0382 for ; Mon, 12 Mar 2012 13:23:22 +0100 (CET) Message-ID: <4F5DEAB9.4010905@hadt.biz> Date: Mon, 12 Mar 2012 13:23:21 +0100 From: Michael Hampicke User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120306 Thunderbird/10.0.1 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] emerge problem - removing old libraries? References: <1331542409.24722.1@numa-i> <20120312100809.308e73f5@digimed.co.uk> In-Reply-To: <20120312100809.308e73f5@digimed.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: de8bd733-c78d-403f-95ab-48c18db334b5 X-Archives-Hash: e583e7220d4a93ce9a5ed5f1087a78c2 > man qfile and look at the section on finding orphan files. > > Emerge portage-utils if you don't have qfile. I just ran # find /usr/lib* -type f -print0 | xargs -0 qfile -o | more an was suprised how much orphans there are, already excluding the python and perl stuff. Here's some suprising stuff: /usr/lib64/systemd/system/canberra-system-shutdown-reboot.service /usr/lib64/systemd/system/console-kit-daemon.service /usr/lib64/systemd/system/canberra-system-shutdown.service /usr/lib64/systemd/system/udev-trigger.service /usr/lib64/systemd/system/udev-control.socket /usr/lib64/systemd/system/dbus.service /usr/lib64/systemd/system/acpid.service /usr/lib64/systemd/system/console-kit-log-system-restart.service /usr/lib64/systemd/system/bluetooth.service /usr/lib64/systemd/system/udev-kernel.socket /usr/lib64/systemd/system/udev.service /usr/lib64/systemd/system/alsa-store.service /usr/lib64/systemd/system/console-kit-log-system-start.service /usr/lib64/systemd/system/udev-settle.service /usr/lib64/systemd/system/canberra-system-bootup.service /usr/lib64/systemd/system/dbus.socket /usr/lib64/systemd/system/alsa-restore.service /usr/lib64/systemd/system/console-kit-log-system-stop.service .... /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libmudflapth.so.0.0.0 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/crtend.o /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgfortran.so.3.0.0 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgfortran.la /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/crtprec80.o /usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.3/libgomp.a .... the gcc stuff is multiple pages long. But I don't think it's a good idea to start messing with gcc's files. And what's with the systemd stuff? I never even installed it. This is a fresh stage3 install from about a week ago. Any thoughts?