From: Hamish Marson <hamish@travellingkiwi.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] emerge kde problems
Date: Fri, 04 Nov 2005 23:33:54 +0000 [thread overview]
Message-ID: <436BEFE2.2070902@travellingkiwi.com> (raw)
In-Reply-To: <200511020200.39687.harmgeerts@home.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Harm Geerts wrote:
> The reason it blocks is because you have other packages installed
> that depend on kde-base/kdebase. For example: kde-base/kdepim and
> kde-base/kdenetwork These are all part of the monolithic packages.
>
> First you'll have to make a choice between monolithic (grouped) and
> segregated (split). Once you've made your choice you should unmerge
> all kde packages that belong to the type you don't want. You can
> recognize monolithic packages as they have a
> "kde-base/<packagename>-meta" replacement which use the split
> packages.
>
Ahh.... Thanks for that. I was wondering how I'd tell the difference..
Pity it wasn't a bit more obvious... e.g. kde-base-split/<package>..
Save me some embarrasment anyway :)
H
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDa+/h/3QXwQQkZYwRAswYAKDHs35KHbi+Vi3YR9QFfxhOAN2V4gCfcwd0
CKCcnOLA54ohdqb1sNWhg7k=
=tSqx
-----END PGP SIGNATURE-----
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2005-11-04 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 9:48 [gentoo-amd64] emerge kde problems Hamish Marson
2005-10-29 9:56 ` [gentoo-amd64] " Anthony Gorecki
2005-10-29 11:24 ` Duncan
2005-11-01 15:32 ` [gentoo-amd64] " Sebastian Redl
2005-11-01 22:59 ` Hamish Marson
2005-11-02 1:00 ` Harm Geerts
2005-11-04 23:33 ` Hamish Marson [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=436BEFE2.2070902@travellingkiwi.com \
--to=hamish@travellingkiwi.com \
--cc=gentoo-amd64@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