Boyd Stephen Smith Jr. wrote:
>
>
> Bringing kde-meta up to version 3.5.6 is going to want to upgrade ALL it's
> dependencies to 3.5.6 (which includes kate).
>
> To maintain different versions of of the various KDE packages, you'll need
> to
> remove the kde-meta package. To make sure 'emerge -u world' (or a
> variant),
> pulls in new version of other packages, you'll want to 'emerge -n' the
> various direct dependencies of kde-meta (kdenetwork-meta etc).
>
> I doubt kate is a direct dependency of kde-meta (I could be wrong). If it
> isn't, one (or more) of the other kde${stuff}-meta packages will also try
> to
> upgrade it. Instead of 'emerge -n'-ing those packages, 'emerge -n' it's
> direct dependencies (one of which should be kate).
>
> You may actually find some packages that you don't care about, feel free to
> not 'emerge -n' them. They will then not be updated by an 'emerge -u
> world'
> and my be removed be 'emerge --depclean' (unless they are a dependency of
> some other package in world)
>
> In fact, I recently removed all the kde${stuff}-meta packages from my
> system
> and only installed the KDE applications I wanted. This might result in
> significant disk space savings, but YMMV. I now have ~90 packages from the
> kde-base category instead of the ~350 pulled in by kde-meta.
>
>
Well, I am doing this the hard way right now. I just check for updates
and update everything but kdelibs and kate manually. So far, so good.
Maybe it will get sorted soon.
Thanks
Dale
:-) :-) :-) :-)
--
www.myspace.com/dalek1967
