| 1 |
On Friday 27 November 2009 15:53:41 Alan McKinnon wrote: |
| 2 |
> On Friday 27 November 2009 17:27:30 James wrote: |
| 3 |
> > Mick <michaelkintzios <at> gmail.com> writes: |
| 4 |
> > > Hmm, I thought that kweather, kate and kfloppy were brought in by some |
| 5 |
> > > meta or other. It seems that I'll have to install these on their own? |
| 6 |
> > |
| 7 |
> > Hello Mick, |
| 8 |
> > |
| 9 |
> > I'm just not certain any more exactly which packages belong to |
| 10 |
> > which meta(kde) package. I think they are added and dropped |
| 11 |
> > over the last few years, resulting in a dynamic grouping |
| 12 |
> > or like those you mentioned, not being picked up by and of the |
| 13 |
> > kde-meta packages. |
| 14 |
> |
| 15 |
> You fellows really need to read the full set of portage man pages. You |
| 16 |
> sound like mechanics that don't know how spanners work. |
| 17 |
|
| 18 |
I'm sure there's a spanner thrown somewhere in the works ... |
| 19 |
|
| 20 |
> The contents of packages is determined by upstream (KDE), not by the gentoo |
| 21 |
> devs. Gentoo devs merely split the monolithic tarballs up into whatever |
| 22 |
> apps the KDE devs say is inside it |
| 23 |
> |
| 24 |
> To find out what is in a -meta package: |
| 25 |
> |
| 26 |
> cat $PORTDIR/kde-base/*-meta/*ebuild |
| 27 |
> |
| 28 |
> There isn't a special tool to do this, much as there isn't a tool to tell |
| 29 |
> you what stuff DEPENDs on say apache. There is a general tool, it's |
| 30 |
> equery depends -a |
| 31 |
[snip ...] |
| 32 |
|
| 33 |
> To find out what depends on kate, kweather and kfloppy, use the correct |
| 34 |
> portage tool: |
| 35 |
> |
| 36 |
> alan@nazgul ~ $ equery depends -a kate |
| 37 |
> * Searching for kate ... |
| 38 |
> kde-base/kdesdk-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
| 39 |
> kde-base/kdesdk-meta-4.3.3 (!kdeprefix ? >=kde-base/kate-4.3.3[-kdeprefix]) |
| 40 |
> (kdeprefix ? |
| 41 |
> >=kde-base/kate-4.3.3:4.3[kdeprefix]) |
| 42 |
|
| 43 |
OK, but I am getting this much - slightly different to yours above: |
| 44 |
|
| 45 |
# equery depends -a kate |
| 46 |
[ Searching for packages depending on kate... ] |
| 47 |
kde-base/kde-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
| 48 |
kde-base/kdesdk-meta-4.3.1 (>=kde-base/kate-4.3.1:4.3[kdeprefix=]) |
| 49 |
|
| 50 |
Now, fair enough, I do not have kde-base/kde-meta installed, so nothing wants |
| 51 |
to pull back in kate when I update world. |
| 52 |
|
| 53 |
> > Let me know if you find a silver bullet (syntax) for discerning |
| 54 |
> > what kde packages are grouped into which meta package or |
| 55 |
> > not grouped at all.. |
| 56 |
> |
| 57 |
> This is Unix. We use grep, sed and awk to find stuff. |
| 58 |
> |
| 59 |
> Much faster than just about anything else... |
| 60 |
|
| 61 |
Right, but only if your regex-fu is good enough. Mine is rather pathetic ... |
| 62 |
:-( |
| 63 |
|
| 64 |
Grateful for all help received to pick up the right spanner. ;-) |
| 65 |
-- |
| 66 |
Regards, |
| 67 |
Mick |
Archives