Gentoo KDE 4.1 Guide

-# emerge -C @kde-4.1 @kdebase-4.1 (only if you are commi= ng from the kdesvn-portage or kde-testing overlay) -# emerge -C $(qfile -C -q -e /usr/kde/%PREFIX%) (replace= %PREFIX% with your kde version, eg. 4) +# emerge -C @kde-4.1 @kdebase-4.1 (only if you are comin= g from the kdesvn-portage or kde-testing overlay) +# emerge -C $(qfile -C -q -e /usr/kde/%PREFIX%) (replace= %PREFIX% with your KDE version, eg. 4)

@@ -55,7 +55,7 @@ =20

As a final step you should remove the old overlay so that there are no c= onflicts -with the KDE ebuilds. You should remove the old unmask and/or keyword da= ta too. +with the KDE ebuilds. You should remove the old unmask and/or keyword da= ta, too.

=20 @@ -73,20 +73,20 @@ =20

The KDE 4.1 ebuilds won't be masked for long (they're currently masked w= hile -solving some issues with the co-existence of kde-3.5 and kde-4.X). Until= the -ebuilds are unmasked, get the package.unmask file from under package.unmask file from under = Documentation/pa= ckage.unmask. If you are running the stable tree you will need to keyword the ebuilds, otherwise skip this step. For those running the stable tree in Gentoo:

=20

-Get the appropriate package.keywords file from the kde-testing overlay t= hat can -be used in your package.keywords file/directory. You can find this file = under -package.keywords file from the kde-tes= ting +overlay that can be used in your package.keywords file/direct= ory. You +can find this file under Documentation/= package.keywords. -Copy the file to the correct location "/etc/portage/package.keywords/", = or add -it to your "/etc/portage/package.keywords" file. +Perform one of the following steps, depending on whether your +/etc/portage/package.keywords is a directory or a file:

=20

@@ -96,7 +96,7 @@
=20
  # cd /etc/portage/
-# cat /path/to/keywords/file >> package.keywords 
+# cat /path/to/keywords/file >> package.keywords
 
=20
 
@@ -105,40 +105,40 @@
 
 Installation
 
-The new kdeprefix use flag
+The new kdeprefix USE flag
 
=20
 
-The new kdeprefix use flag allows users to choose between an FHS complia=
nt
+The new kdeprefix USE flag allows users to choose between an FHS complia=
nt
 install (-kdeprefix) or a slotted install in the KDE prefix (+kdeprefix)=
.
 
=20
 
 If kdeprefix is disabled (default) KDE is installed into the FHS complia=
nt
 location, i.e. /usr. That means that all of the files are put under /usr=
. This
-is the desired behavior for most users. The drawback of the FHS complian=
t
+is the desired behaviour for most users. The drawback of the FHS complia=
nt
 install is that it will not be possible to have more than one minor vers=
ion of
 KDE side by side (previous behaviour), e.g. KDE 4.1 and 4.2.
 
=20
 
-This restriction does not apply to KDE 3.5 (different eclasses) or live =
versions
-(as they will continue to be installed in the /usr/kde/${live-slot}. You=
 can
-have a non kdeprefix version of KDE 4.1, KDE 3.5 and a live version of K=
DE
-installed on the same system.
+This restriction does not apply to KDE 3.5 (which uses different eclasse=
s) or
+live versions (as they will continue to be installed under
+/usr/kde/${live-slot}. You can have a non-kdeprefix version o=
f KDE
+4.1, KDE 3.5 and a live version of KDE installed on the same system.
 
=20
 
-If kdeprefix is enabled then KDE is installed into /usr/kde/${SLOT}, whi=
ch
-allows you to install KDE 4.1, 4.2, 4.3 etc in /usr/kde/4.1, /usr/kde/4.=
2,
-/usr/kde/4.3 for example.
+If kdeprefix is enabled then KDE is installed into /usr/kde/${SLOT}=
,
+which allows you to install KDE 4.1, 4.2, 4.3, etc. in /usr/kde/4.1=
,
+/usr/kde/4.2, and /usr/kde/4.3 for example.
 
=20
 
 If you want to move between kdeprefix and -kdeprefix (or vice-versa), it=
 is
-recommended that you unmerge KDE and then emerge it with the modified fl=
ag. If
-this is not done KDE installations can have trouble finding certain
-libraries/plugins.
+recommended that you unmerge all KDE packages and then emerge it with th=
e
+modified flag. If this is not done, KDE installations can have trouble f=
inding
+certain libraries/plugins.
 
=20
 
@@ -148,7 +148,7 @@
 
=20
 
-One of the new features provided by portage 2.2 is sets.
+One of the new features provided by Portage 2.2 is sets.
 
=20
 
@@ -156,16 +156,16 @@
 packages, with the added bonus that users may choose to remove from the =
default
 sets any packages they do not want. There is still some discussion going=
 on
 before we can put sets in the Portage tree. Thus, grab the sets from the
-kde-testing overlay kde-testing overlay sets
-directory and put the ones you like in "/etc/portage/sets" =
- you
+directory and put the ones you like in /etc/portage/sets --=
 you
 can browse the list of sets provided by the KDE team in the overlay.
 
=20
 
 Amongst others, there are sets for each KDE tarball - @kdeaccessibility,
 @kdeadmin, @kdeartwork, @kdebase, @kdeedu, @kdegames, @kdegraphics,
-@kdemultimedia, @kdenetwork, @kdepim, @kdesdk, @kdetoys and @kdeutils. T=
here is
+@kdemultimedia, @kdenetwork, @kdepim, @kdesdk, @kdetoys, and @kdeutils. =
There is
 also a set of sets (the equivalent to the old kde-meta package) @kde, an=
d the
 same for specific versions @kde-3.5 and @kde-4x, a set for KDE deps @kde=
deps, a
 set for optional packages @kdeoptional and a set for the split qt packag=
es
@@ -173,26 +173,27 @@
 
=20
 
-One can install the complete KDE by doing emerge -av @kde. The sp=
ecific
+One can install the complete KDE by running emerge -av @kde. The =
specific
 version equivalents are very useful to uninstall an old version, e.g. emerge
 -C @kde-3.5, or to reinstall all packages from a specific version, e=
.g.
 emerge -av1 @kde-4x. Advanced features, like removing any unwante=
d
-packages from a set, will be supported in a future release of portage - =
you can
+packages from a set, will be supported in a future release of Portage --=
 you can
 read more about it in Marius
-Mauch (genone) blog. This code has already been commited to Portag=
e's svn
-and will allow to reinstall all installed packages of a set with emerge =
-av
-@<set>/@installled or to have a /etc/portage/sets/kdebase-unwanted=
 set and
-then run emerge -av @kdebase-@kdebase-unwanted.
+Mauch's (genone) blog. This code has already been committed to Por=
tage's
+SVN and will allow to reinstall all installed packages of a set with =
emerge
+-av @<set>/@installled or to have a
+/etc/portage/sets/kdebase-unwanted set and then run emerge=
 -av
+@kdebase-@kdebase-unwanted.
 
=20
 
-We strongly recommend that you install the @kdebase set in order to get =
a full
-KDE 4 session. The example below would install the kdebase set and the k=
degames
-set.
+We strongly recommend that you install the kdebase set in order t=
o get a
+full KDE 4 session. The example below would install the kdebase s=
et and
+the kdegames set.
 
=20
-+ # emerge @kdebase @kdegames
 
=20
@@ -202,8 +203,9 @@
 
=20
 
-All KDE 4.1 ebuilds require portage-2.2_rc11 or greater, which has imple=
mented
-everything in the new EAPI 2 specification used in these ebuilds.
+All KDE 4.1 ebuilds require sys-apps/portage-2.2_rc11 or greater,=
 which
+has implemented everything in the new EAPI 2 specification used in these
+ebuilds.
 
=20
 
@@ -213,7 +215,7 @@
 
=20
 
-This method is provided to ease the transition to the new sets. There wi=
ll no
+This method is provided to ease the transition to the new sets. There wi=
ll be no
 meta ebuilds for KDE 4.2.
 
=20
@@ -233,14 +235,14 @@
 KDE stores its configuration files in the ~/.kde directory by def=
ault. In
 the Gentoo ebuilds this has been changed in KDE 4.1 to allow for better
 integration of KDE 3.5 and 4.1 when using the same user account. If you =
export
-KDEHOME this behaviour will be overridden. It is strongly recommended th=
at you
-do not do this. KDEHOME will make KDE 3.5 and 4.1 use the same configura=
tion
-directory which is not usually desired.
+$KDEHOME this behaviour will be overridden. It is strongly recommended t=
hat you
+do not do this. $KDEHOME will make KDE 3.5 and 4.1 use the same configur=
ation
+directory which is usually not desired.
 
=20
 
 KDE 3.5 uses ~/.kde and the default FHS (-kdeprefix) KDE 4.1 uses
-~/.kde4. If you install KDE 4.1 using the kdeprefix use flag then=
 the
+~/.kde4. If you install KDE 4.1 using the kdeprefix USE flag then=
 the
 configuration directory will default to ~/.kde4.1, ~/.kde4.2 etc.
 The advantage of this is that KDE 3.5 and 4.1 can be run from the same u=
ser
 account without clobbering settings. Moving backwards in version, i.e. 4=
.1 to
@@ -253,12 +255,12 @@
 before logging in. For example,
 
=20
-+ $ cp -r ~/.kde ~/.kde4
 
=20
 
-If this is successful then your settings should all be migrated. If not =
it is
+If this is successful, then your settings should all be migrated. If not=
, it is
 possible to log out and remove the new configuration directory to start =
with a
 clean configuration directory.
 
@@ -273,32 +275,36 @@
 
=20
 
-If you used the kde-testing overlay before the testing branch was merged=
 back
-into the master overlay, you're going to get collision-protection errors=
 when
-you try to update the new ebuilds will show up as belonging to a new slo=
t [NS].
-This is caused by a move from the 4 to 4.1 SLOT. You have =
2
+If you used the kde-testing overlay before the testing branch was=
 merged
+back into the master overlay, you're going to get collision-protection e=
rrors
+when you try to update; the new ebuilds will show up as belonging to a n=
ew slot
+[NS]. This is caused by a move from the 4 to 4.1 SLOT. You=
 have 2
 choices in this case:
 
=20
-
-Unmerging all of KDE and install it again
-
+
+
+
+Unmerging all of KDE and installing it again
+
=20
  # emerge -C @kde-4.1
 
=20
-
-Changing the SLOT of the installed ebuilds in the VDB.
-
+
+
+
+Changing the SLOT of the installed ebuilds in the VDB
+
=20
 
-Changing the SLOT in the VDB may cause issues and is not recommended - d=
o it at
+Changing the SLOT in the VDB may cause issues and is not recommended -- =
do it at
 your own risk. You should instead do the above. If you really want to do=
 that,
 please grab the
-script from the kde-testing overlay. You should only run it if you
-understand what it script does and after you double check it.
+script from the kde-testing overlay. You should only run it=
 if you
+understand what it does and after you double checked it.
 
=20
 
@@ -308,17 +314,17 @@
=20
  # change_slot kde 4 4.1
-# After you confirm that it works as expected (you should see SLOTS as 4=
.1 and not 4)
+# (After you confirm that it works as expected (you should see =
SLOTS as 4.1 and not 4))
 # change_slot kde 4 4.1 Y
 
=20
 
 
 
-Removing kde-3.5
+Removing KDE 3.5
 
=20
-+ # emerge -C @kde-3.5
 
=20
@@ -357,7 +363,7 @@
=20
 
 This ebuild contains various plasmoids that were requested by users (if =
you find
-others that would be useful to our user community please contact us, svn=
 version
+others that would be useful to our user community please contact us, SVN=
 version
 will not be added and it must work with KDE 4.1).
 
=20
@@ -379,9 +385,9 @@
 
=20
 
-This ebuild should be used if you want your gtk applications to use a si=
milar
-them to the Qt/KDE applications. Configuration can be found in
-systemsetings->Apperance->GTK Styles and Fonts.
+This ebuild should be used if you want your GTK applications to use a th=
eme
+similar to the Qt/KDE applications. Configuration can be found in
+systemsetings->Appearance->GTK Styles and Fonts.
 
=20
 
@@ -391,16 +397,16 @@
 
=20
 
-Another approach to making gtk/qt3/qt4 applications looks the same. You =
must
-also install x11-themes/qtcurve-qt4 for this to work with Qt 4/KDE 4
-applications.
+This is another approach to making GTK/Qt 3/Qt 4 applications looks the =
same.
+You must also install x11-themes/qtcurve-qt4 for this to work wit=
h Qt
+4/KDE 4 applications.
 
=20
 
 
 
 
-Uninstalling KDE-4x
+Uninstalling KDE 4.x
 
 Removing all KDE packages