public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] removing kde4(sets)
Date: Thu, 29 Oct 2009 14:17:23 -0500	[thread overview]
Message-ID: <58965d8a0910291217y33d65e79ne14dea5331900317@mail.gmail.com> (raw)
In-Reply-To: <20091029165316.4312b99a@zaphod.digimed.co.uk>

On Thu, Oct 29, 2009 at 11:53 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 29 Oct 2009 11:45:54 -0500, Paul Hartman wrote:
>
>> >> Are there any tricks to remove all of kde4, or do
>> >> I have to do it manually?
>> >
>> > The set and the meta-package pull in basically the same packages.
>> > Unmerge the set, emerge kde-meta then do a depclean to catch any
>> > stragglers.
>>
>> I would just delete the set from the world_sets file, then emerge
>> kde-meta, then depclean... much easier than unmerging everything and
>> recompiling it.
>
> Sorry, that's what I meant. I was thinking that unmerging a set was like
> unmerging a meta-package, that only the set itself would go.

Ah, okay, we meant the same thing then. :) AFAK emerge -C @set will
remove everything in @set but there's no portage command to remove the
set definition without unmerging what's in it.  I could be wrong on
that, though.



  reply	other threads:[~2009-10-29 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 15:04 [gentoo-user] removing kde4(sets) James
2009-10-29 15:41 ` Neil Bothwick
2009-10-29 16:45   ` Paul Hartman
2009-10-29 16:53     ` Neil Bothwick
2009-10-29 19:17       ` Paul Hartman [this message]
2009-10-29 19:21         ` Alan McKinnon
2009-10-29 20:03         ` Neil Bothwick
2009-10-29 19:09 ` Alan McKinnon
2009-10-30 18:53   ` [gentoo-user] " James
2009-10-30 20:33     ` Alan McKinnon
2009-10-31  0:46       ` Neil Bothwick
2009-10-31 19:31         ` Alan McKinnon

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=58965d8a0910291217y33d65e79ne14dea5331900317@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --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