Re: KDE emerge issue (package)

On Tue, 15 Oct 2002 09:29:04 -0400
[email protected] wrote:

> I emerged KDE over the course of yesterday and this morning.  The last package mentioned was kde-3.0.4 (I think).  I emerged it and it proceeded very quickly.  It didn't seem to do any compiling but also gave no noticeable errors.  When I re-run "emerge --pretend kde", it shows the same package!  There is an "R" between the brackets.  What is this telling me?

It's telling you that if you /were/ to run the command "emerge kde" again then it would (R)einstall that package. If a newer version were available it would say "U" instead for (U)pgrade. In this case, it would probably do nothing if you ran that command, read on to find out why ...

The package "kde-base/kde" is a /meta-package/. It's just a stub which doesn't actually compile anything, but has dependencies on all the other parts of KDE (kde-base/kdelibs, kde-base/kdebase, kde-base/kdenetwork ... etc ...). Consequently, Portage compiles and installs *all* of the available KDE modules. The alternative would have been that you emerge the parts that your want individaully. Type the following to see what it really did and in what order (the grep shows only the KDE related dependencies):

   emerge --pretend --emptytree kde | grep kde-base

If you had done it manually you would have wanted to merge these packages in this order:

   kde-base/arts
   kde-base/kdelibs
   kde-base/kdebase

After that you can add whatever you want.

--kerframil