Aleksandr wrote:
> Can I just do `emerge -B kde` (only build packages) and then `emerge -K
> kde` (emerge them)? It would be the best way for me, but is it really
> the same as `emerge kde`?
emerge --help says that
--buildpkgonly (-B short option)
Creates a binary package, but does not merge it to the
system. This has the restriction that unsatisfied dependencies
must not exist for the desired package as they cannot be used if
they do not exist on the system.
So, you should probably do an emerge --onlydeps for all the individual kde
packages first (emerge --onlydeps kde will pull in all the packages, so that
won't work). Note though that this will pull in at least arts, kdelibs,
kdebase, kdenetwork and kdemultimedia. Which basically defeats the whole
purpose.
OTOH, from what I remember from the 3.1.3->3.1.4 upgrade, KDE will work just
fine if you restart it after upgrading kdelibs and kdebase. So, you could use
the GUI for the majority of the process. Although don't quote me on this one.
--
Jani-Matti H�tinen
--
[EMAIL PROTECTED] mailing list
