From: Dirk Heinrichs <dirk.heinrichs@online.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kde 3.5 packages blocking each other
Date: Fri, 12 Jun 2009 22:58:27 +0200 [thread overview]
Message-ID: <200906122258.27712.dirk.heinrichs@online.de> (raw)
In-Reply-To: <543f3b9c0906121345h6d174c8ahf607051c0cc8a536@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Am Freitag 12 Juni 2009 22:45:49 schrieb Francisco Ares:
> And how do I tell if an ebuild is monolithic or not?
The monolithic ones install larger parts of KDE, and usually have the same
names as the original source packages offered at KDE.org.
The split ebuilds, well, split those packages into their individual
applications, so you have ebuilds for konqueror (which is also part of
kdenetwork) or kmail (kdepim). In addition, there are the "-meta" ebuilds,
which have the same name as the monolitic ones, but with -meta appended
(kdepim-meta). Those usually install the same applications than monolithic
ebuilds, but as split ebuilds.
So, when you install kde, you get a complete KDE from monolithic ebuilds and
when you install kde-meta, you get a complete KDE from split ebuilds.
That's also the reason why they block each other. When you have kdepim
installed, you already got kmail, so you shouldn't install kmail from the
split ebuild again.
HTH...
Dirk
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2009-06-12 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 20:24 [gentoo-user] kde 3.5 packages blocking each other Francisco Ares
2009-06-12 20:33 ` Dirk Heinrichs
2009-06-12 20:45 ` Francisco Ares
2009-06-12 20:58 ` Dirk Heinrichs [this message]
2009-06-12 23:54 ` Francisco Ares
2009-06-13 8:58 ` Alan McKinnon
2009-06-15 1:32 ` Francisco Ares
2009-06-15 6:57 ` Alan McKinnon
2009-06-16 1:19 ` Francisco Ares
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=200906122258.27712.dirk.heinrichs@online.de \
--to=dirk.heinrichs@online.de \
--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