From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE (mono to meta) migration
Date: Thu, 22 Jun 2006 19:26:18 +0200 [thread overview]
Message-ID: <200606221926.23539.bo.andresen@zlin.dk> (raw)
In-Reply-To: <loom.20060622T174816-134@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2598 bytes --]
On Thursday 22 June 2006 18:28, James wrote:
> have looked at threads on this issue from 12jun06
> and 2jun06
> and http://www.gentoo.org/doc/en/kde-split-ebuilds.xml.
> By the way, this doc is good for explaining the issues,
> but does not explain a clear method to perform the migration
> form mono to meta......
Did you look at [1] too?
> Is there an easy way to remove all of the kde packages before
> migration to kde-meta?
Sure. But it would remove packages that the meta packages depend on too.
kde-base/kdelibs takes a long time to compile and hence shouldn't be removed
as you still need it. Unless of course you need to upgrade it anyway. This
might be feasible:
#cd /var/db/pkg && emerge -Cva `ls -d kde-base/* | grep -v -r 'kdelibs\|arts'`
It will remove everything in the kde-base category except kdelibs and arts.
Make sure to check what it removes before doing it. It shouldn't be more than
13 packages.
[SNIP]
> But if meta
> is going away, like the monolithic kde packaging (eventually)
> I'd rather go straight to the split kde package system.
> Comments and Recommendations on kde-meta's future?
Why would you think the kde-meta aka the split packages would be going away?
They certainly won't.
> emerge -atv kde-meta
> lists many packages and I'm too lazy to remove them all by
> hand....
Actually there aren't a lot of monolithic packages. [1] lists them all in a
box in section 2. If you have all of them you still need to remove only 13
packages.
> These are the packages that would be merged, in reverse order:
> Calculating dependencies... done!
> .[blocks B ] =kde-base/kdemultimedia-3.5* (is blocking
> kde-base/kaboodle-3.5.2) .[blocks B ] =kde-base/kdemultimedia-3.5* (is
> blocking
> kde-base/kdemultimedia-kappfinder-data-3.5.2)
This tells you that kde-base/kdemultimedia blocks both kaboodle and
kdemultimedia-kappfinder-data. You only need to remove the one package
kdemultimedia. It just blocks a lot of packages that are pulled in by
kde-meta.
[SNIP]
> From mono to split? Some gentoo/kde systems I manage will want
> to go to the split system or a few kde-meta packages and the
> rest of the kde(split) apps individually installed.
Do what I said above or just remove the few packages manually when they block
something. There really aren't that many. emerging any split package will
work just as well as the meta packages. You should only use the meta packages
if you wan't everything.
[1] http://www.gentoo.org/doc/en/kde-config.xml
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-22 17:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 16:28 [gentoo-user] KDE (mono to meta) migration James
2006-06-22 17:26 ` Bo Ørsted Andresen [this message]
2006-06-22 18:15 ` [gentoo-user] " James
2006-06-22 19:05 ` Bo Ørsted Andresen
2006-06-22 20:12 ` James
2006-06-22 20:24 ` Bo Ørsted Andresen
2006-06-24 15:25 ` James
2006-06-24 15:47 ` Bo Ørsted Andresen
2006-06-24 16:05 ` James
2006-06-24 16:28 ` Bo Ørsted Andresen
2006-06-24 17:21 ` James
2006-06-24 17:32 ` Bo Ørsted Andresen
2006-06-27 1:02 ` James
2006-06-27 7:20 ` Neil Bothwick
2006-06-22 21:48 ` Mick
2006-06-22 21:56 ` Bo Ørsted Andresen
2006-06-22 22:18 ` Mick
2006-06-22 17:43 ` [gentoo-user] " Neil Bothwick
2006-06-22 18:21 ` [gentoo-user] " James
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=200606221926.23539.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