From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] prune dangers
Date: Sun, 5 Aug 2007 16:27:18 +0200 [thread overview]
Message-ID: <200708051627.24596.bo.andresen@zlin.dk> (raw)
In-Reply-To: <20070718003310.74d4e3e6@zaphod.digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Wednesday 18 July 2007 01:33:10 Neil Bothwick wrote:
> 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
[SNIP]
> > In particular, GNOME and X windows?
>
> No. In particular the toolchain. GNOME and X work quite happily without
> slotted packages in general.
Well.. GNOME doesn't work all that well without glib-2.x and gtk+-2.x. KDE
wouldn't work particularly well without qt-3.x either and gnupg-1.9.x would
become pretty broken by removing gnupg-1.4.x... All in all --prune is rarely
a good idea.. ;)
--
Bo Andresen
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-08-05 14:37 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
2007-08-05 14:27 ` Bo Ørsted Andresen [this message]
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=200708051627.24596.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--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