| 1 |
On Saturday 28 November 2009 02:01:22 Mick wrote: |
| 2 |
> > To find out what depends on kate, kweather and kfloppy, use the correct |
| 3 |
> > portage tool: |
| 4 |
> > |
| 5 |
> > alan@nazgul ~ $ equery depends -a kate |
| 6 |
> > * Searching for kate ... |
| 7 |
> > kde-base/kdesdk-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
| 8 |
> > kde-base/kdesdk-meta-4.3.3 (!kdeprefix ? |
| 9 |
> > >=kde-base/kate-4.3.3[-kdeprefix]) (kdeprefix ? |
| 10 |
> > >=kde-base/kate-4.3.3:4.3[kdeprefix]) |
| 11 |
> |
| 12 |
> OK, but I am getting this much - slightly different to yours above: |
| 13 |
> |
| 14 |
> # equery depends -a kate |
| 15 |
> [ Searching for packages depending on kate... ] |
| 16 |
> kde-base/kde-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
| 17 |
> kde-base/kdesdk-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
| 18 |
> |
| 19 |
> Now, fair enough, I do not have kde-base/kde-meta installed, so nothing |
| 20 |
> wants to pull back in kate when I update world. |
| 21 |
> |
| 22 |
|
| 23 |
That's normal. The pre-defined sets in kde-testing overlay explicitly list |
| 24 |
kate in the @kde set for that reason. |
| 25 |
|
| 26 |
I suppose one could make several useful -meta packages DEPEND on kate, as many |
| 27 |
users want kate and do not want the entire kdesdk package. But that causes the |
| 28 |
same app to appear in more than one -meta package and the devs seem to want to |
| 29 |
avoid that - there is a strict one-to-one mapping between what the -meta |
| 30 |
packages install and what is shipped in the upstream tarballs by KDE |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
alan dot mckinnon at gmail dot com |
Archives