jmbsvicetto 08/10/06 03:25:40
Modified: kde4-guide.xml
Log:
Updated the kde4-guide to reflect the changes from moving the ebuilds to the tree.
Revision Changes Path
1.2 xml/htdocs/proj/en/desktop/kde/kde4-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml?r1=1.1&r2=1.2
Index: kde4-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- kde4-guide.xml 29 Sep 2008 01:00:53 -0000 1.1
+++ kde4-guide.xml 6 Oct 2008 03:25:39 -0000 1.2
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml,v 1.1 2008/09/29 01:00:53 jmbsvicetto Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml,v 1.2 2008/10/06 03:25:39 jmbsvicetto Exp $ -->
<guide link="proj/en/desktop/kde/kde4.xml" lang="en">
<title>Gentoo KDE 4.1 Guide</title>
@@ -16,7 +16,7 @@
</author>
<abstract>
-This guide demonstrates how to setup KDE 4.1 using the KDE team's git overlay (kde-testing). It will be updated later when the ebuilds are moved into the tree.
+This guide demonstrates how to setup KDE 4.1 using the ebuilds in the tree. Some tools from the KDE team's git overlay (kde-testing) will be used.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -31,12 +31,12 @@
<section>
<title>Removing old KDE versions</title>
<body>
- <p>In order to minimize issues, it is best to begin with a clean enviroment. You will need to uninstall any beta or 4.0.X release (this is needed if you are moving from any other overlay and in particular if you plan to use the -kdeprefix use flag - FHS install). Two possible ways or removing old KDE 4 installations are:</p>
+ <p>In order to minimize issues, it is best to begin with a clean enviroment. You will need to uninstall any beta or 4.0.X release (this is needed if you are moving from any overlay and in particular if you plan to use the -kdeprefix use flag - FHS install). Two possible ways or removing old KDE 4 installations are:</p>
<pre caption="Unmerging commands">
-# <i>emerge -C @kde-4.1 @kdebase-4.1</i> <comment>(only if you are comming from the kdesvn-portage overlay)</comment>
+# <i>emerge -C @kde-4.1 @kdebase-4.1</i> <comment>(only if you are comming from the kdesvn-portage or kde-testing overlay)</comment>
# <i>emerge -C $(qfile -C -q -e /usr/kde/%PREFIX%)</i> <comment>(replace %PREFIX% with your kde version, eg. 4)</comment>
</pre>
- <pre caption="Unmerging commands (only applicable if you are moving from other overlay)">
+ <pre caption="Unmerging commands (only applicable if you are moving from an overlay)">
# <i>cd /path/to/old/overlay/</i>
# <i>emerge -C $(find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print "="$1"/"$3}')</i>
</pre>
@@ -47,63 +47,21 @@
</chapter>
<chapter>
- <title>Grabbing overlay</title>
- <section>
- <title>Using layman</title>
- <body>
- <pre caption="layman command">
-# <i>layman -fS; layman -a kde-testing</i></pre>
- </body>
- </section>
- <section>
- <title>Using git</title>
- <body>
- <pre caption="git command">
-# <i>git clone git://git.overlays.gentoo.org/proj/kde.git /PATH/WHERE/TO/PUT/OVERLAY</i></pre>
- </body>
- </section>
- <section>
- <body>
- <note>The KDE 4.1 ebuilds make use of EAPI 2. Please use portage-2.2_rc11 or greater, if you run an otherwise stable profile then you must add portage to your package.keywords file.</note>
- <note>Don't forget to modify /etc/make.conf to add the overlay path to PORTDIR_OVERLAY, or to add the support for layman as required.</note>
- </body>
- </section>
-</chapter>
-
-<chapter>
<title>Unmasking/Keywording</title>
<section>
- <title>Using the bundled package.keywords/kde file</title>
+ <title>Using the package.keywords/kde file from the kde-testing overlay</title>
<body>
- <p>The KDE 4.1 ebuilds available from the kde-testing overlay are not masked (the masks in package.mask have been updated accordingly) and so there is no need to unmask them. 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:</p>
+ <p>The KDE 4.1 ebuilds won't be masked for long (they're currently masked while 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 <uri link="http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob_plain;f=Documentation/package.unmask/kde;hb=master">Documentation/package.unmask</uri>. 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:</p>
<note>This is the recomended way of keywording the KDE packages.</note>
- <p>This overlay provides an appropriate package.keywords file that can be used in your package.keywords file/directory. You can find this file in "Documentation/package.keywords" directory. Copy it to the correct location "/etc/portage/package.keywords/" (preferably make a symlink to it), or add it to your "/etc/portage/package.keywords" file.</p>
+ <p>Get the appropriate package.keywords file from the kde-testing overlay that can be used in your package.keywords file/directory. You can find this file under <uri link="http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob_plain;f=Documentation/package.keywords/kde;hb=master">Documentation/package.keywords</uri>. Copy the file to the correct location "/etc/portage/package.keywords/", or add it to your "/etc/portage/package.keywords" file.</p>
<pre caption="Adding the file to the package.keywords directory">
# <i>cd /etc/portage/package.keywords</i>
-# <i>ln -s /path/to/overlay/Documentation/package.keywords/kde .</i>
+# <i>cp /path/to/keywords/file .</i>
</pre>
<pre caption="Adding the file to the package.keywords file">
# <i>cd /etc/portage/</i>
-# <i>cat /path/to/overlay/Documentation/package.keywords/kde >> package.keywords </i>
- </pre>
- </body>
- </section>
- <section>
- <title>Creating the file from the packages in the overlay</title>
- <body>
- <pre caption="Adding keywords to the package.keywords directory">
-# <i>cd /path/to/our/overlay/</i>
-# <i>find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print $1"/"$2}' >> /etc/portage/package.keywords/kde4x</i>
-# <i>cd /usr/portage/</i>
-# <i>find ./x11-libs/qt-* -type d |sed -e "s:./::" |awk -F'/' '{print $1"/"$2}' | uniq >> /etc/portage/package.keywords/kde4x</i>
+# <i>cat /path/to/keywords/file >> package.keywords </i>
</pre>
- <pre caption="Adding keywords to the package.keywords file">
-# <i>cd /path/to/our/overlay/</i>
-# <i>find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print $1"/"$2}' >> /etc/portage/package.keywords</i>
-# <i>cd /usr/portage/</i>
-# <i>find ./x11-libs/qt-* -type d |sed -e "s:./::" |awk -F'/' '{print $1"/"$2}' | uniq >> /etc/portage/package.keywords</i>
- </pre>
- <note>There are some dependencies which require keywording that are not in this list. Keyword them as necessary.</note>
</body>
</section>
</chapter>
@@ -124,7 +82,7 @@
<title>Using sets</title>
<body>
<p>One of the new features provided by portage 2.2 is sets.</p>
- <p>Sets allow the KDE team to provide a complete replacement for the monolithic packages, with the added bonus that users may choose to remove from the default sets any packages they do not want. Look in the sets directory for a list of the sets provided by the KDE team.</p>
+ <p>Sets allow the KDE team to provide a complete replacement for the monolithic 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 <uri link="http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=tree;f=sets;h=e44f270a37083da16da6f1b70c226169e44c4237;hb=master">sets directory</uri> and put the ones you like in <e>"/etc/portage/sets"</e> - you can browse the list of sets provided by the KDE team in the overlay.</p>
<p>Amongst others, there are sets for each KDE tarball - @kdeaccessibility, @kdeadmin, @kdeartwork, @kdebase, @kdeedu, @kdegames, @kdegraphics, @kdemultimedia, @kdenetwork, @kdepim, @kdesdk, @kdetoys and @kdeutils. There is also a set of sets (the equivalent to the old kde-meta package) @kde, and the same for specific versions @kde-3.5 and @kde-4x, a set for KDE deps @kdedeps, a set for optional packages @kdeoptional and a set for the split qt packages @qt-split.</p>
<p>One can install the complete KDE by doing <e>emerge -av @kde</e>. The specific version equivalents are very useful to uninstall an old version, e.g. <e>emerge -C @kde-3.5</e>, or to reinstall all packages from a specific version, e.g. <e>emerge -av1 @kde-4x</e>. Advanced features, like removing any unwanted packages from a set, will be supported in a future release of portage - you can read more about it in <uri link="http://planet.gentoo.org/developers/genone/2008/09/29/more_extensions_to_package_set_support">Marius Mauch (genone) blog</uri>. This code has already been commited to Portage'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 <e>emerge -av @kdebase-@kdebase-unwanted</e>.</p>
<p>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 kdegames set.</p>
@@ -158,7 +116,7 @@
</section>
</chapter>
<chapter>
- <title>Migration from KDE 3.X</title>
+ <title>Migration from earlier releases</title>
<section>
<title>Configuration transition</title>
<body>
@@ -166,6 +124,24 @@
</body>
</section>
<section>
+ <title>Upgrading from the kde-testing overlay</title>
+ <body>
+ <p>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 slot [NS]. This is caused by a move from the <e>4</e> to <e>4.1</e> SLOT. You have 2 choices in this case:</p>
+ <p>Unmerging all of KDE and install it again</p>
+ <pre caption="Unmerging kde-4.1">
+# <i>emerge -C @kde-4.1</i>
+ </pre>
+ <p>Changing the SLOT of the installed ebuilds in the VDB.</p>
+ <p>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 <uri link="http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob_plain;f=Documentation/change_slot;hb=master">the script</uri> from the kde-testing overlay. You should only run it if you understand what it script does and after you double check it.</p>
+ <note>Be warned that this script is known to eat your kittens or steal all your cookies.</note>
+ <pre caption="Running change_slot to update the slot from 4 to 4.1">
+# <i>change_slot kde 4 4.1</i>
+# After you confirm that it works as expected (you should see SLOTS as 4.1 and not 4)
+# <i>change_slot kde 4 4.1 Y</i>
+ </pre>
+ </body>
+ </section>
+ <section>
<title>Removing kde-3.5</title>
<body>
<pre caption="Unmerging kde-3.5">
|
