1 |
On Friday 27 November 2009 17:27:30 James wrote: |
2 |
> Mick <michaelkintzios <at> gmail.com> writes: |
3 |
> > Hmm, I thought that kweather, kate and kfloppy were brought in by some |
4 |
> > meta or other. It seems that I'll have to install these on their own? |
5 |
> |
6 |
> Hello Mick, |
7 |
> |
8 |
> I'm just not certain any more exactly which packages belong to |
9 |
> which meta(kde) package. I think they are added and dropped |
10 |
> over the last few years, resulting in a dynamic grouping |
11 |
> or like those you mentioned, not being picked up by and of the |
12 |
> kde-meta packages. |
13 |
|
14 |
You fellows really need to read the full set of portage man pages. You sound |
15 |
like mechanics that don't know how spanners work. |
16 |
|
17 |
The contents of packages is determined by upstream (KDE), not by the gentoo |
18 |
devs. Gentoo devs merely split the monolithic tarballs up into whatever apps |
19 |
the KDE devs say is inside it |
20 |
|
21 |
To find out what is in a -meta package: |
22 |
|
23 |
cat $PORTDIR/kde-base/*-meta/*ebuild |
24 |
|
25 |
There isn't a special tool to do this, much as there isn't a tool to tell you |
26 |
what stuff DEPENDs on say apache. There is a general tool, it's |
27 |
equery depends -a |
28 |
|
29 |
> Some time ago kde-meta ( the package that calls other kde-meta(sub |
30 |
> group packages) was to be done away with. |
31 |
|
32 |
You are mistaken. |
33 |
|
34 |
That has never ever been the case. The monolithic ebuilds have been done away |
35 |
with in favour of split ebuilds. This has been in planning for 2 years right |
36 |
from the beginning of the KDE-3.5 series |
37 |
|
38 |
> Now, magically, |
39 |
> kde-meta is back, after the "Sets" solution seems to be |
40 |
> too cumbersome for those of us that want a simple and easy |
41 |
> method to install a bulk of kde packages. |
42 |
|
43 |
Citation please :-) |
44 |
|
45 |
Zac has never to my knowledge said that sets are too cumbersome for regular |
46 |
people. Sets are not yet in stable portage because he wants the feature to be |
47 |
tested more. Therefore sets cannot be exposed in the portage tree. That's why |
48 |
defined sets are only distributed in the overlays, not in the tree. |
49 |
|
50 |
|
51 |
> Other than this '10,000' foot view, you'll have to get more |
52 |
> precise information from the gentoo kde devs or others, |
53 |
> as I just do not know...... |
54 |
|
55 |
To find out what depends on kate, kweather and kfloppy, use the correct |
56 |
portage tool: |
57 |
|
58 |
alan@nazgul ~ $ equery depends -a kate |
59 |
* Searching for kate ... |
60 |
kde-base/kdesdk-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
61 |
kde-base/kdesdk-meta-4.3.3 (!kdeprefix ? >=kde-base/kate-4.3.3[-kdeprefix]) |
62 |
(kdeprefix ? >=kde-base/kate-4.3.3:4.3[kdeprefix]) |
63 |
|
64 |
alan@nazgul ~ $ equery depends -a kweather |
65 |
* Searching for kweather ... |
66 |
kde-base/kdetoys-meta-4.3.1 (>=kde-base/kweather-4.3.1:4.3[kdeprefix=]) |
67 |
kde-base/kdetoys-meta-4.3.3 (!kdeprefix ? >=kde-base/kweather-4.3.3[- |
68 |
kdeprefix]) |
69 |
(kdeprefix ? >=kde- |
70 |
base/kweather-4.3.3:4.3[kdeprefix]) |
71 |
|
72 |
alan@nazgul ~ $ equery depends -a kfloppy |
73 |
* Searching for kfloppy ... |
74 |
kde-base/kdeutils-meta-4.3.1 (floppy ? >=kde- |
75 |
base/kfloppy-4.3.1:4.3[kdeprefix=]) |
76 |
kde-base/kdeutils-meta-4.3.3 (floppy & !kdeprefix ? >=kde-base/kfloppy-4.3.3[- |
77 |
kdeprefix]) |
78 |
(floppy & kdeprefix ? >=kde- |
79 |
base/kfloppy-4.3.3:4.3[kdeprefix]) |
80 |
|
81 |
|
82 |
So kate DEPENDS on kdesdk (it's a dev tool, emerge it individually if you just |
83 |
want the editor) |
84 |
kweather DEPENDS on kde-toys |
85 |
kfloppy DEPENDS on kdeutils iff USE=floppy |
86 |
|
87 |
> You'd think there'd be a master listing of (kde-4) packages |
88 |
> and which one belong to which meta-package or what not; |
89 |
> if not a script to tool to reveal this information.... |
90 |
|
91 |
There is. See above. |
92 |
|
93 |
> Let me know if you find a silver bullet (syntax) for discerning |
94 |
> what kde packages are grouped into which meta package or |
95 |
> not grouped at all.. |
96 |
|
97 |
This is Unix. We use grep, sed and awk to find stuff. |
98 |
|
99 |
Much faster than just about anything else... |
100 |
|
101 |
-- |
102 |
alan dot mckinnon at gmail dot com |