Re: [gentoo-user] kde 3.5 packages blocking each other

[Alan McKinnon]

On Saturday 13 June 2009 01:54:45 Francisco Ares wrote:
> Thanks a lot!

It's not completely obvious from Dirk's post (what he said is completely 
accurate though), but kde-3.5.10 will not receive monolithic ebuilds (dev 
decision). If you want kde-3.5.10, there is only one way to do it -

Unmerge your existing kde monolithic packages
Rememerge the new kde split packages

There's a good migration guide at gentoo.org, called "Migrating to KDE split 
ebuilds" or some such. A quick search will find it for you.



 
>
> Francisco
>
> On Fri, Jun 12, 2009 at 5:58 PM, Dirk Heinrichs
<dirk.heinrichs@××××××.de>wrote:
> > 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

-- 
alan dot mckinnon at gmail dot com