From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Coping with KDE upgrades
Date: Sun, 19 Nov 2006 13:13:13 -0600 [thread overview]
Message-ID: <200611191313.13431.bss03@volumehost.net> (raw)
In-Reply-To: <9acccfe50611191052v36fbecd3ob4b7aad6d1e7f3ec@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]
On Sunday 19 November 2006 12:52, "Kevin O'Gorman" <kogorman@gmail.com>
wrote about '[gentoo-user] Coping with KDE upgrades':
> I converted to KDE modular some time ago with considerable trepidation.
> Now I'm faced with the updates that came out this week, and I'd like to
> take advantage of the opportunity this offers to dispense with (that is,
> unmerge) the many parts of KDE I will never use.
I'm there with you.
> The problem is obvious and unavoidable: there are 231 parts that
> currently are in my world file, and I do not know what all of them
> do. I can cherry-pick a few that are obvious throw-aways by removing
> them from world, and waiting to see if they get updated anyway because
> they're actually needed.
The only package that was in my world file was kde-meta. That brings in
everything. How did you get 213 entries anyway? Forgetting to use -1
(--oneshot) as needed?
> Does anybody have advice about how to improve that process? Would it
> be better to remove all but the obvious keepers?
The way I'm slimming things down, I removed kde-meta from world, and then
did emerge -p --depclean. I look over the (*LONG*) list and when I see an
application I use, I add it to my world file with emerge -n. After I'm
fairly sure I've caught everything I'll let the depclean actually remove
packages.
> I'm not looking forward to the pains-taking process of vetting each and
> every one of the 231, but I don't want to be spending the time to
> recompile the presumed multitude that I never ever use.
Unfortunately I still have a long list of packages to "confirm" that I
don't use before unmerging. An "advantage" to my situtation is that I
still have all of kde, but updates are only applied to things that are
depended upon by my world file.
You'll have to do some manual work, but you can always build binary
packages of anything before unmerging it so that re-merging it is quite
sort. grep-ing your process list for package names (or vice-versa) can
easily confirm packages as used. Also, if your filesystem keeps track of
atimes, you can probably use those to help make decisions.
I'm not sure I *directly* addressed your questions, but HTH.
--
"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 --]
next prev parent reply other threads:[~2006-11-19 19:16 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. [this message]
2006-11-19 19:47 ` Richard Fish
[not found] ` <20061119222507.GB5830@sympatico.ca>
2006-11-20 13:02 ` Boyd Stephen Smith Jr.
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=200611191313.13431.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