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