| 1 |
jmbsvicetto 08/09/29 01:00:53 |
| 2 |
|
| 3 |
Modified: index.xml |
| 4 |
Added: kde4-guide.xml |
| 5 |
Log: |
| 6 |
Added the new KDE4 guide and updated the links on the index page. |
| 7 |
|
| 8 |
Revision Changes Path |
| 9 |
1.41 xml/htdocs/proj/en/desktop/kde/index.xml |
| 10 |
|
| 11 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml?rev=1.41&view=markup |
| 12 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml?rev=1.41&content-type=text/plain |
| 13 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml?r1=1.40&r2=1.41 |
| 14 |
|
| 15 |
Index: index.xml |
| 16 |
=================================================================== |
| 17 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml,v |
| 18 |
retrieving revision 1.40 |
| 19 |
retrieving revision 1.41 |
| 20 |
diff -u -r1.40 -r1.41 |
| 21 |
--- index.xml 20 Sep 2008 15:16:35 -0000 1.40 |
| 22 |
+++ index.xml 29 Sep 2008 01:00:53 -0000 1.41 |
| 23 |
@@ -288,7 +288,8 @@ |
| 24 |
<uri link="kde-expat-upgrading.xml">Upgrading to KDE 3.5.7/8: Frequently |
| 25 |
Asked Questions</uri> |
| 26 |
</li> |
| 27 |
- <li><uri link="kde4.xml">KDE 4.0 Guide</uri></li> |
| 28 |
+ <li><uri link="kde4-guide.xml">KDE 4.X Guide (new version)</uri></li> |
| 29 |
+ <li><uri link="kde4.xml">KDE 4.0 Guide (old and outdated)</uri></li> |
| 30 |
</ul> |
| 31 |
</li> |
| 32 |
</ul> |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
1.1 xml/htdocs/proj/en/desktop/kde/kde4-guide.xml |
| 37 |
|
| 38 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml?rev=1.1&view=markup |
| 39 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml?rev=1.1&content-type=text/plain |
| 40 |
|
| 41 |
Index: kde4-guide.xml |
| 42 |
=================================================================== |
| 43 |
<?xml version="1.0" encoding="UTF-8"?> |
| 44 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 45 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/kde/kde4-guide.xml,v 1.1 2008/09/29 01:00:53 jmbsvicetto Exp $ --> |
| 46 |
|
| 47 |
<guide link="proj/en/desktop/kde/kde4.xml" lang="en"> |
| 48 |
<title>Gentoo KDE 4.1 Guide</title> |
| 49 |
|
| 50 |
<author title="Author"> |
| 51 |
<mail link="tomas.chvatal@×××××.com">Tomáš Chvátal</mail> |
| 52 |
</author> |
| 53 |
<author title="Author"> |
| 54 |
<mail link="jmbsvicetto"/> |
| 55 |
</author> |
| 56 |
<author title="Author"> |
| 57 |
<mail link="cryos" /> |
| 58 |
</author> |
| 59 |
|
| 60 |
<abstract> |
| 61 |
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. |
| 62 |
</abstract> |
| 63 |
|
| 64 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 65 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 66 |
<license/> |
| 67 |
|
| 68 |
<version>0.2</version> |
| 69 |
<date>2008-09-28</date> |
| 70 |
|
| 71 |
<chapter> |
| 72 |
<title>Cleaning up</title> |
| 73 |
<section> |
| 74 |
<title>Removing old KDE versions</title> |
| 75 |
<body> |
| 76 |
<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> |
| 77 |
<pre caption="Unmerging commands"> |
| 78 |
# <i>emerge -C @kde-4.1 @kdebase-4.1</i> <comment>(only if you are comming from the kdesvn-portage overlay)</comment> |
| 79 |
# <i>emerge -C $(qfile -C -q -e /usr/kde/%PREFIX%)</i> <comment>(replace %PREFIX% with your kde version, eg. 4)</comment> |
| 80 |
</pre> |
| 81 |
<pre caption="Unmerging commands (only applicable if you are moving from other overlay)"> |
| 82 |
# <i>cd /path/to/old/overlay/</i> |
| 83 |
# <i>emerge -C $(find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print "="$1"/"$3}')</i> |
| 84 |
</pre> |
| 85 |
<p>As a final step you should remove the old overlay so that there are no conflicts with the KDE ebuilds. You should remove the old unmask and/or keyword data too.</p> |
| 86 |
<note>Don't forget to run depclean in order to uninstall any dependant packages.</note> |
| 87 |
</body> |
| 88 |
</section> |
| 89 |
</chapter> |
| 90 |
|
| 91 |
<chapter> |
| 92 |
<title>Grabbing overlay</title> |
| 93 |
<section> |
| 94 |
<title>Using layman</title> |
| 95 |
<body> |
| 96 |
<pre caption="layman command"> |
| 97 |
# <i>layman -fS; layman -a kde-testing</i></pre> |
| 98 |
</body> |
| 99 |
</section> |
| 100 |
<section> |
| 101 |
<title>Using git</title> |
| 102 |
<body> |
| 103 |
<pre caption="git command"> |
| 104 |
# <i>git clone git://git.overlays.gentoo.org/proj/kde.git /PATH/WHERE/TO/PUT/OVERLAY</i></pre> |
| 105 |
</body> |
| 106 |
</section> |
| 107 |
<section> |
| 108 |
<body> |
| 109 |
<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> |
| 110 |
<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> |
| 111 |
</body> |
| 112 |
</section> |
| 113 |
</chapter> |
| 114 |
|
| 115 |
<chapter> |
| 116 |
<title>Unmasking/Keywording</title> |
| 117 |
<section> |
| 118 |
<title>Using the bundled package.keywords/kde file</title> |
| 119 |
<body> |
| 120 |
<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> |
| 121 |
<note>This is the recomended way of keywording the KDE packages.</note> |
| 122 |
<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> |
| 123 |
<pre caption="Adding the file to the package.keywords directory"> |
| 124 |
# <i>cd /etc/portage/package.keywords</i> |
| 125 |
# <i>ln -s /path/to/overlay/Documentation/package.keywords/kde .</i> |
| 126 |
</pre> |
| 127 |
<pre caption="Adding the file to the package.keywords file"> |
| 128 |
# <i>cd /etc/portage/</i> |
| 129 |
# <i>cat /path/to/overlay/Documentation/package.keywords/kde >> package.keywords </i> |
| 130 |
</pre> |
| 131 |
</body> |
| 132 |
</section> |
| 133 |
<section> |
| 134 |
<title>Creating the file from the packages in the overlay</title> |
| 135 |
<body> |
| 136 |
<pre caption="Adding keywords to the package.keywords directory"> |
| 137 |
# <i>cd /path/to/our/overlay/</i> |
| 138 |
# <i>find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print $1"/"$2}' >> /etc/portage/package.keywords/kde4x</i> |
| 139 |
# <i>cd /usr/portage/</i> |
| 140 |
# <i>find ./x11-libs/qt-* -type d |sed -e "s:./::" |awk -F'/' '{print $1"/"$2}' | uniq >> /etc/portage/package.keywords/kde4x</i> |
| 141 |
</pre> |
| 142 |
<pre caption="Adding keywords to the package.keywords file"> |
| 143 |
# <i>cd /path/to/our/overlay/</i> |
| 144 |
# <i>find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print $1"/"$2}' >> /etc/portage/package.keywords</i> |
| 145 |
# <i>cd /usr/portage/</i> |
| 146 |
# <i>find ./x11-libs/qt-* -type d |sed -e "s:./::" |awk -F'/' '{print $1"/"$2}' | uniq >> /etc/portage/package.keywords</i> |
| 147 |
</pre> |
| 148 |
<note>There are some dependencies which require keywording that are not in this list. Keyword them as necessary.</note> |
| 149 |
</body> |
| 150 |
</section> |
| 151 |
</chapter> |
| 152 |
|
| 153 |
<chapter> |
| 154 |
<title>Installation</title> |
| 155 |
<section> |
| 156 |
<title>The new kdeprefix use flag</title> |
| 157 |
<body> |
| 158 |
<p>The new kdeprefix use flag allows users to choose between an FHS compliant install (-kdeprefix) or a slotted install in the KDE prefix (+kdeprefix).</p> |
| 159 |
<p>If kdeprefix is disabled (default) KDE is installed into the FHS compliant 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 compliant install is that it will not be possible to have more than one minor version of KDE side by side (previous behaviour), e.g. KDE 4.1 and 4.2.</p> |
| 160 |
<note>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 KDE installed on the same system.</note> |
| 161 |
<p>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, /usr/kde/4.3 for example.</p> |
| 162 |
<warn>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 flag. If this is not done KDE installations can have trouble finding certain libraries/plugins.</warn> |
| 163 |
</body> |
| 164 |
</section> |
| 165 |
<section> |
| 166 |
<title>Using sets</title> |
| 167 |
<body> |
| 168 |
<p>One of the new features provided by portage 2.2 is sets.</p> |
| 169 |
<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> |
| 170 |
<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> |
| 171 |
<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> |
| 172 |
<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> |
| 173 |
<pre caption="emerge KDE"> |
| 174 |
# <i>emerge @kdebase @kdegames</i> |
| 175 |
</pre> |
| 176 |
<note>If you want to check the list of sets known to Portage run the following: <e>emerge --list-sets</e></note> |
| 177 |
<note>All KDE 4.1 ebuilds require portage-2.2_rc11 or greater, which has implemented everything in the new EAPI 2 specification used in these ebuilds.</note> |
| 178 |
</body> |
| 179 |
</section> |
| 180 |
<section> |
| 181 |
<title>KDE meta packages</title> |
| 182 |
<body> |
| 183 |
<note>This method is provided to ease the transition to the new sets. There will no meta ebuilds for KDE 4.2.</note> |
| 184 |
<pre caption="emerge meta packages"> |
| 185 |
# <i>emerge kde-meta:4.1</i></pre> |
| 186 |
</body> |
| 187 |
</section> |
| 188 |
</chapter> |
| 189 |
<chapter> |
| 190 |
<title>Configuration</title> |
| 191 |
<section> |
| 192 |
<body> |
| 193 |
<p>KDE stores its configuration files in the <e>~/.kde</e> directory by default. 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 that you do not do this. KDEHOME will make KDE 3.5 and 4.1 use the same configuration directory which is not usually desired.</p> |
| 194 |
<p>KDE 3.5 uses <e>~/.kde</e> and the default FHS (-kdeprefix) KDE 4.1 uses <e>~/.kde4</e>. If you install KDE 4.1 using the kdeprefix use flag then the configuration directory will default to <e>~/.kde4.1</e>, <e>~/.kde4.2</e> etc. The advantage of this is that KDE 3.5 and 4.1 can be run from the same user account without clobbering settings. Moving backwards in version, i.e. 4.1 to 3.5, is not supported.</p> |
| 195 |
<p>Settings are not migrated by default. If you want to attempt to migrate your settings you should copy your old configuration directory to the new location before logging in. For example,</p> |
| 196 |
<pre caption="copy configuration directory"> |
| 197 |
$ <i>cp -r ~/.kde ~/.kde4</i></pre> |
| 198 |
<p>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.</p> |
| 199 |
</body> |
| 200 |
</section> |
| 201 |
</chapter> |
| 202 |
<chapter> |
| 203 |
<title>Migration from KDE 3.X</title> |
| 204 |
<section> |
| 205 |
<title>Configuration transition</title> |
| 206 |
<body> |
| 207 |
<p>TODO</p> |
| 208 |
</body> |
| 209 |
</section> |
| 210 |
<section> |
| 211 |
<title>Removing kde-3.5</title> |
| 212 |
<body> |
| 213 |
<pre caption="Unmerging kde-3.5"> |
| 214 |
# <i>emerge -C @kde-3.5</i> |
| 215 |
</pre> |
| 216 |
<note>Run depclean in order to remove all dependent packages.</note> |
| 217 |
</body> |
| 218 |
</section> |
| 219 |
<section> |
| 220 |
<title>No Desktop icon</title> |
| 221 |
<body> |
| 222 |
<p>KDE 4, as it moves towards a semantic desktop, did not bundle an icon for the desktop.</p> |
| 223 |
<p>The desktop icon can be replaced with the standard folder icon using the following command.</p> |
| 224 |
<pre caption="sed command"> |
| 225 |
$ <i>sed -i -e "s:Icon=desktop:Icon=folder:g" ~/Desktop/.directory</i></pre> |
| 226 |
</body> |
| 227 |
</section> |
| 228 |
</chapter> |
| 229 |
<chapter> |
| 230 |
<title>Hints</title> |
| 231 |
<section> |
| 232 |
<title>kde-misc/plasmoids</title> |
| 233 |
<body> |
| 234 |
<p>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 will not be added and it must work with KDE 4.1).</p> |
| 235 |
</body> |
| 236 |
</section> |
| 237 |
<section> |
| 238 |
<title>x11-themes/plasma-themes</title> |
| 239 |
<body> |
| 240 |
<p>This ebuild contains various plasma themes. The procedure for requesting additional themes is the same as that for plasmoids.</p> |
| 241 |
</body> |
| 242 |
</section> |
| 243 |
<section> |
| 244 |
<title>x11-themes/gtk-engines-qt</title> |
| 245 |
<body> |
| 246 |
<p>This ebuild should be used if you want your gtk applications to use a similar them to the Qt/KDE applications. Configuration can be found in systemsetings->Apperance->GTK Styles and Fonts.</p> |
| 247 |
</body> |
| 248 |
</section> |
| 249 |
<section> |
| 250 |
<title>x11-themes/gtk-engines-qtcurve</title> |
| 251 |
<body> |
| 252 |
<p>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.</p> |
| 253 |
</body> |
| 254 |
</section> |
| 255 |
</chapter> |
| 256 |
<chapter> |
| 257 |
<title>Uninstalling KDE-4x</title> |
| 258 |
<section> |
| 259 |
<title>Removing all KDE packages</title> |
| 260 |
<body> |
| 261 |
<p>In order to remove all KDE 4 packages and dependant packages:</p> |
| 262 |
<pre caption="Unmerging commands"> |
| 263 |
# <i>emerge -C @kde-4x</i> |
| 264 |
# <i>cd /path/to/our/overlay/</i> |
| 265 |
# <i>emerge -C $(find ./ -name \*.ebuild |sed -e "s:.ebuild::" -e "s:./::" |awk -F'/' '{print "="$1"/"$3}')</i></pre> |
| 266 |
</body> |
| 267 |
</section> |
| 268 |
<section> |
| 269 |
<title>Rebuilding the application database</title> |
| 270 |
<body> |
| 271 |
<p>To rebuild the KDE 3 application database run:</p> |
| 272 |
<pre caption="kbuildsycoca command"> |
| 273 |
# kbuildsycoca --noincremental</pre> |
| 274 |
</body> |
| 275 |
</section> |
| 276 |
</chapter> |
| 277 |
</guide> |
Archives