public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Coping with KDE upgrades
Date: Mon, 20 Nov 2006 07:02:02 -0600	[thread overview]
Message-ID: <200611200702.11424.bss03@volumehost.net> (raw)
In-Reply-To: <20061119222507.GB5830@sympatico.ca>

[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]

On Sunday 19 November 2006 16:25, Philip Webb <purslow@sympatico.ca> wrote 
about 'Re: [gentoo-user] Coping with KDE upgrades':
> 061119 Kevin O'Gorman wrote:
> > Now I'm faced with the updates that came out this week
> > and I'd like to unmerge the many parts of KDE I will never use.
> > Would it be better to remove all but the obvious keepers?
>
> You need  3  things :
>
>   kdelibs

This doesn't have to be in your world file because it will be pulled in as 
a dependency of applications that require those libraries.

>   kdebase-startkde (which emerges  16  other pkgs first)

Yes, this is a really easy one to miss, but it provides some fairly 
essential scripts.  It's certainly possible to run "KDE" without it, by 
writing your own scripts, but that's almost getting to the point where 
your are running KDE application in your own custom desktop environment.

Of course, it's fairly arbitrary where the line is between just running KDE 
applications and running "KDE".  Certainly you are running "KDE" if you 
are running it as defined by upstream (kdelibs, kdebase, kdegames, kdepim, 
etc.; the whole #!) which is achieved in Gentoo by emerging kde-meta 
(modular) or kde (monolithic).  Also, I doubt anyone would say you are 
running KDE if you have amaroK in your Gnome session, even if you are 
using kwin as your window manager.  There's a lot of middle ground though.

> So start by unmerging everything, then merge 3.5.5 as above.

No need to unmerge first. 1) edit your world file, 2) emerge -n anything 
want to keep, 3) emerge -a --depclean.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2006-11-20 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 18:52 [gentoo-user] Coping with KDE upgrades Kevin O'Gorman
2006-11-19 19:13 ` Boyd Stephen Smith Jr.
2006-11-19 19:47   ` Richard Fish
     [not found] ` <20061119222507.GB5830@sympatico.ca>
2006-11-20 13:02   ` Boyd Stephen Smith Jr. [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=200611200702.11424.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --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