David Corbin wrote:
On Sunday 31 July 2005 05:59 pm, Neil Bothwick wrote:
On Sun, 31 Jul 2005 17:28:49 -0400, Daniel D Jones wrote:
[EMAIL PROTECTED]:/# emerge --pretend kde-meta
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] =kde-base/kdebase-3.4* (is blocking
kde-base/kscreensaver-3.4.1)
You currently have KDE installed with the monolithic ebuilds. to stay
with them, use "emerge -av kde" instead of kde-meta (there's not a lot of
point in using the split ebuilds if you're going to install everything
anyway). Alternatively, you'll have to unmerge that various kdebase, and
probably some of the other monolithic ebuilds, before merging kde-meta.
Don't unmerge kdelibs or arts, they are the same whichever set of ebuilds
you use.
What's the best way to find out what all the "split ebuilds" are?
David
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.
$ equery which kde-meta
/usr/portage/kde-base/kde-meta/kde-meta-3.4.2.ebuild
Unfortunately, equery depgraph does not seem to be very helpful for this type
of query.
Zac
--
[email protected] mailing list
