1 |
David Corbin wrote: |
2 |
> On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote: |
3 |
> |
4 |
>>On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote: |
5 |
>> |
6 |
>>>root@Merlin:/# emerge --pretend kde-meta |
7 |
>>> |
8 |
>>>These are the packages that I would merge, in order: |
9 |
>>> |
10 |
>>>Calculating dependencies ...done! |
11 |
>>>[blocks B ] =kde-base/kdebase-3.4* (is blocking |
12 |
>>>kde-base/kscreensaver-3.4.1) |
13 |
>> |
14 |
>>You currently have KDE installed with the monolithic ebuilds. to stay |
15 |
>>with them, use "emerge -av kde" instead of kde-meta (there's not a lot of |
16 |
>>point in using the split ebuilds if you're going to install everything |
17 |
>>anyway). Alternatively, you'll have to unmerge that various kdebase, and |
18 |
>>probably some of the other monolithic ebuilds, before merging kde-meta. |
19 |
>>Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds |
20 |
>>you use. |
21 |
> |
22 |
> |
23 |
> What's the best way to find out what all the "split ebuilds" are? |
24 |
> |
25 |
> David |
26 |
|
27 |
|
28 |
The kde-meta ebuild should cover all of the split ebuilds. If you read that you will discover that it depends on other meta packages. Read the ebuilds of those meta packages to find out what they depend on, and so on. |
29 |
|
30 |
$ equery which kde-meta |
31 |
/usr/portage/kde-base/kde-meta/kde-meta-3.4.2.ebuild |
32 |
|
33 |
Unfortunately, equery depgraph does not seem to be very helpful for this type of query. |
34 |
|
35 |
Zac |
36 |
-- |
37 |
gentoo-user@g.o mailing list |