From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Removing KDE 3.5? Or reason to keep it around?
Date: Sat, 27 Feb 2010 05:19:27 +0200 [thread overview]
Message-ID: <hma2vo$3d8$1@dough.gmane.org> (raw)
In-Reply-To: <897612.13661.qm@web65412.mail.ac4.yahoo.com>
On 02/27/2010 04:15 AM, BRM wrote:
> ----- Original Message ----
>
>> From: Neil Bothwick<neil@digimed.co.uk> To:
>> gentoo-user@lists.gentoo.org On Fri, 26 Feb 2010 06:34:18 -0800
>> (PST), BRM wrote:
>>> Aside from that, I'm not sure I have ever really run "emerge
>>> --depclean", but I also rarely uninstall anything, but don't
>>> install things left or right to try out either, so typically
>>> upgrades are all I need to do.
>> You should still run --depclean as dependencies change and you
>> could still have plenty of no longer needed ones installed.
>
> Okay - so I ran "emerge --depclean -a" and got the below. I tried
> running "emerge world -vuDNa" as specified, but that didn't resolve
> it either.
>
> I tried looking in the world file (/var/lib/portage/world) but didn't
> find any entries that felt safe to remove.
"Safe" as to what? If something is in the world file that you didn't
explicitly request, then it doesn't belong there. For example, if you
have "x11-libs/qt-gui" in world, you should delete it. The world file
should not contain dependencies, it should only contain the stuff you
emerged directly.
To give an example, if you emerge "media-video/smplayer", then that one
will end up in the world file. But smplayer will also pull-in qt and
mplayer. Those do not go in the world file. When you unmerge smplayer
again, qt and mplayer will not be unmerged unless you run "emerge
--depclean". However, if qt and mplayer end up being in the world file
anyway, it means you made a mistake at some point; like emerging
something that is a dependency but forgot to specify the "-1" (or
"--oneshot") option to emerge.
So if you see something in the world file that you know don't need
directly (and I doubt you need qt directly; KDE for example needs it,
you, as a person, don't) it's safe to remove.
Of course always make a backup first :P
next prev parent reply other threads:[~2010-02-27 4:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 4:06 [gentoo-user] Removing KDE 3.5? Or reason to keep it around? BRM
2010-02-26 4:17 ` [gentoo-user] " Nikos Chantziaras
2010-02-26 5:39 ` Dale
2010-02-26 14:34 ` BRM
2010-02-26 15:10 ` Alex Schuster
2010-02-26 16:10 ` BRM
2010-02-26 18:30 ` Nikos Chantziaras
2010-02-26 18:01 ` Dale
2010-02-26 23:20 ` Neil Bothwick
2010-02-27 0:24 ` Dale
2010-02-27 2:15 ` BRM
2010-02-27 3:11 ` Dale
2010-02-27 4:34 ` BRM
2010-02-27 5:15 ` Dale
2010-02-27 11:38 ` Neil Bothwick
2010-02-27 3:19 ` Nikos Chantziaras [this message]
2010-02-27 3:45 ` Dale
2010-02-27 5:21 ` BRM
2010-02-27 6:53 ` Nikos Chantziaras
2010-02-27 7:21 ` Mick
2010-02-27 11:39 ` Neil Bothwick
2010-02-27 11:41 ` Neil Bothwick
2010-02-27 17:12 ` Dale
2010-02-27 18:26 ` Neil Bothwick
2010-02-27 19:16 ` Dale
2010-02-27 19:42 ` BRM
2010-02-27 20:16 ` Dale
2010-02-27 11:42 ` Neil Bothwick
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='hma2vo$3d8$1@dough.gmane.org' \
--to=realnc@arcor.de \
--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