From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] prune dangers
Date: Wed, 18 Jul 2007 00:33:10 +0100 [thread overview]
Message-ID: <20070718003310.74d4e3e6@zaphod.digimed.co.uk> (raw)
In-Reply-To: <bf6b6d5c0707171600h34e52302pfabe5e65b3255e84@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Tue, 17 Jul 2007 23:00:48 +0000, Thufir wrote:
> It seems that prune would break all sorts of software, yes?
Yes, which is why the emerge man page states
--prune (-P)
WARNING: This action can remove important packages! Prune
looks at each installed package and attempts to remove all
but the most recently installed version. Prune ignores
slots, if you require a slot-aware Prune use emerge --clean.
Prune may inadvertently remove important packages from your
system. Use --clean instead unless you really know what
you're doing.
> In particular, GNOME and X windows?
No. In particular the toolchain. GNOME and X work quite happily without
slotted packages in general.
--
Neil Bothwick
... ebius tagline. This is a moebius tagline. This is a mo ...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-17 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 23:00 [gentoo-user] prune dangers Thufir
2007-07-17 23:33 ` Neil Bothwick [this message]
2007-08-05 14:27 ` Bo Ørsted Andresen
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=20070718003310.74d4e3e6@zaphod.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