| 1 |
Boyd Stephen Smith Jr. wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> Bringing kde-meta up to version 3.5.6 is going to want to upgrade ALL it's |
| 5 |
> dependencies to 3.5.6 (which includes kate). |
| 6 |
> |
| 7 |
> To maintain different versions of of the various KDE packages, you'll need |
| 8 |
> to |
| 9 |
> remove the kde-meta package. To make sure 'emerge -u world' (or a |
| 10 |
> variant), |
| 11 |
> pulls in new version of other packages, you'll want to 'emerge -n' the |
| 12 |
> various direct dependencies of kde-meta (kdenetwork-meta etc). |
| 13 |
> |
| 14 |
> I doubt kate is a direct dependency of kde-meta (I could be wrong). If it |
| 15 |
> isn't, one (or more) of the other kde${stuff}-meta packages will also try |
| 16 |
> to |
| 17 |
> upgrade it. Instead of 'emerge -n'-ing those packages, 'emerge -n' it's |
| 18 |
> direct dependencies (one of which should be kate). |
| 19 |
> |
| 20 |
> You may actually find some packages that you don't care about, feel free to |
| 21 |
> not 'emerge -n' them. They will then not be updated by an 'emerge -u |
| 22 |
> world' |
| 23 |
> and my be removed be 'emerge --depclean' (unless they are a dependency of |
| 24 |
> some other package in world) |
| 25 |
> |
| 26 |
> In fact, I recently removed all the kde${stuff}-meta packages from my |
| 27 |
> system |
| 28 |
> and only installed the KDE applications I wanted. This might result in |
| 29 |
> significant disk space savings, but YMMV. I now have ~90 packages from the |
| 30 |
> kde-base category instead of the ~350 pulled in by kde-meta. |
| 31 |
> |
| 32 |
> |
| 33 |
|
| 34 |
Well, I am doing this the hard way right now. I just check for updates |
| 35 |
and update everything but kdelibs and kate manually. So far, so good. |
| 36 |
Maybe it will get sorted soon. |
| 37 |
|
| 38 |
Thanks |
| 39 |
|
| 40 |
Dale |
| 41 |
|
| 42 |
:-) :-) :-) :-) |
| 43 |
|
| 44 |
-- |
| 45 |
www.myspace.com/dalek1967 |
Archives