Gentoo Archives: gentoo-doc-cvs

From: Xavier Neys <neysx@××××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: metadoc.xml kde-config.xml kde-split-ebuilds.xml
Date: Sat, 26 Apr 2008 19:21:11
Message-Id: E1JppxE-0003wc-JU@stork.gentoo.org
1 neysx 08/04/26 19:21:00
2
3 Modified: metadoc.xml kde-config.xml kde-split-ebuilds.xml
4 Log:
5 #219345 Kra^H^HDE docs moved to its project space. Good riddance.
6
7 Revision Changes Path
8 1.211 xml/htdocs/doc/en/metadoc.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.xml?rev=1.211&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.xml?rev=1.211&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.xml?r1=1.210&r2=1.211
13
14 Index: metadoc.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v
17 retrieving revision 1.210
18 retrieving revision 1.211
19 diff -u -r1.210 -r1.211
20 --- metadoc.xml 11 Apr 2008 23:59:51 -0000 1.210
21 +++ metadoc.xml 26 Apr 2008 19:21:00 -0000 1.211
22 @@ -1,8 +1,8 @@
23 <?xml version="1.0" encoding="UTF-8"?>
24 <!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd">
25 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.210 2008/04/11 23:59:51 nightmorph Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.211 2008/04/26 19:21:00 neysx Exp $ -->
27 <metadoc lang="en">
28 - <version>1.132</version>
29 + <version>1.133</version>
30 <members>
31 <lead>neysx</lead>
32 <member>cam</member>
33 @@ -255,7 +255,7 @@
34 <file id="uml">/doc/en/uml.xml</file>
35 <file id="java">/doc/en/java.xml</file>
36 <file id="openafs">/doc/en/openafs.xml</file>
37 - <file id="kde-config">/doc/en/kde-config.xml</file>
38 + <file id="kde-config">/proj/en/desktop/kde/kde-config.xml</file>
39 <file id="nano-basics-guide">/doc/en/nano-basics-guide.xml</file>
40 <file id="shoutcast-config">/doc/en/shoutcast-config.xml</file>
41 <file id="vdr-guide">/doc/en/vdr-guide.xml</file>
42 @@ -352,7 +352,7 @@
43 <file id="metadoc-guide">/proj/en/gdp/doc/metadoc-guide.xml</file>
44 <file id="hpc-howto">/doc/en/hpc-howto.xml</file>
45 <file id="gnap-userguide">/proj/en/base/embedded/gnap-userguide.xml</file>
46 - <file id="kde-split-ebuilds">/doc/en/kde-split-ebuilds.xml</file>
47 + <file id="kde-split-ebuilds">/proj/en/desktop/kde/kde-split-ebuilds.xml</file>
48 <file id="grub-error-guide">/doc/en/grub-error-guide.xml</file>
49 <file id="usb-guide">/doc/en/usb-guide.xml</file>
50 <file id="liveusb">/doc/en/liveusb.xml</file>
51
52
53
54 1.34 xml/htdocs/doc/en/kde-config.xml
55
56 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-config.xml?rev=1.34&view=markup
57 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-config.xml?rev=1.34&content-type=text/plain
58 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-config.xml?r1=1.33&r2=1.34
59
60 Index: kde-config.xml
61 ===================================================================
62 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-config.xml,v
63 retrieving revision 1.33
64 retrieving revision 1.34
65 diff -u -r1.33 -r1.34
66 --- kde-config.xml 28 Nov 2007 19:26:51 -0000 1.33
67 +++ kde-config.xml 26 Apr 2008 19:21:00 -0000 1.34
68 @@ -1,19 +1,16 @@
69 <?xml version='1.0' encoding='UTF-8'?>
70
71 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-config.xml,v 1.33 2007/11/28 19:26:51 neysx Exp $ -->
72 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-config.xml,v 1.34 2008/04/26 19:21:00 neysx Exp $ -->
73
74 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
75
76 -<guide link="/doc/en/kde-config.xml">
77 +<guide redirect="/proj/en/desktop/kde/kde-config.xml">
78
79 <title>The KDE Configuration HOWTO</title>
80
81 <author title="Author">
82 <mail link="swift@g.o">Sven Vermeulen</mail>
83 </author>
84 -<author title="Editor">
85 - <mail link="greg_g@g.o">Gregorio Guidi</mail>
86 -</author>
87
88 <abstract>
89 One of the most used desktop environments is KDE. This guide tries to describe
90 @@ -24,826 +21,19 @@
91 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
92 <license/>
93
94 -<version>1.22</version>
95 -<date>2007-06-23</date>
96 -
97 -<chapter>
98 -<title>What is the K Desktop Environment?</title>
99 -<section>
100 -<title>The Project</title>
101 -<body>
102 -
103 -<p>
104 -The <uri link="http://www.kde.org">KDE Project</uri> is a free software project
105 -dedicated to the development of KDE, an open source graphical desktop
106 -environment for Linux and Unix workstations. The development is carried out by
107 -several hundred software engineers from all over the world committed to free
108 -software development. See also <uri
109 -link="http://www.kde.org/whatiskde/project.php">What is the KDE Project</uri>.
110 -</p>
111 -
112 -</body>
113 -</section>
114 -<section>
115 -<title>The Software</title>
116 -<body>
117 -
118 -<p>
119 -The K Desktop Environment is an easy-to-use desktop environment built around a
120 -well thought out application framework to allow for application
121 -interoperability, drag n drop and so on. Apart from the essential components,
122 -the KDE environment also provides ready-to-use applications for 101 tasks: file
123 -management, Internet browsing, office applications, e-mail handling, ...
124 -Everything is covered by the KDE project.
125 -</p>
126 -
127 -<p>
128 -The KDE environment is available in more than 70 languages and has an immense
129 -user base. For those interested, there are lots of <uri
130 -link="http://www.kde.org/screenshots/">screen shots</uri> available. For more
131 -information on KDE, read the <uri link="http://www.kde.org/whatiskde/">What is
132 -KDE?</uri> article on <uri link="http://www.kde.org">KDE.org</uri>.
133 -</p>
134 -
135 -</body>
136 -</section>
137 -<section>
138 -<title>The Community</title>
139 -<body>
140 -
141 -<p>
142 -Many KDE-based community sites exist. On <uri
143 -link="http://www.kdenews.org">KDEnews.org</uri> you'll find the latest news on
144 -KDE generally. <uri link="http://www.kdedevelopers.org">KDEdevelopers.org</uri>
145 -is specifically focussed on KDE development, while <uri
146 -link="http://www.kde-forum.org">KDE-forum</uri> is better suited for the large
147 -masses. More links can be found on the <uri
148 -link="http://www.kde.org/family/">KDE Family page</uri>.
149 -</p>
150 +<version>2</version>
151 +<date>2008-04-26</date>
152
153 -</body>
154 -</section>
155 -</chapter>
156 <chapter>
157 -<title>Installing KDE</title>
158 -<section>
159 -<title>What do you need?</title>
160 -<body>
161 -
162 -<p>
163 -If you're interested in installing KDE (or KDE support), you will have to make
164 -sure that your USE variable contains the <c>kde</c> flag, and either the
165 -<c>qt3</c> or <c>qt4</c> flag (or both). Qt is the graphical widget library that
166 -KDE uses, and <c>qt3</c> is for version 3.x, while <c>qt4</c> will build support
167 -for the newer Qt 4.x library. Neither USE flag is necessary for installing KDE.
168 -However, there are a few packages that offer you the choice of using either the
169 -<c>qt3</c> or <c>qt4</c> libraries.
170 -</p>
171 -
172 -<p>
173 -You should also add <c>hal</c> to your USE variable now if you want to add support
174 -for mounting devices automatically as explained below in
175 -<uri link="#kde_device_mounting">Setup KDE to Mount Devices</uri>.
176 -</p>
177 -
178 -<p>
179 -If you do not want to use <uri link="http://www.arts-project.org/">aRts</uri>
180 -for your all-around multimedia, disable the <c>arts</c> USE flag (it is active
181 -by default).
182 -</p>
183 -
184 -<note>
185 -The Gentoo 2006.1 release introduced a number of new profiles, including the
186 -<c>desktop</c> subprofile. You may want to switch to this subprofile, if it
187 -exists for your architecture, as it contains a number of default USE flag
188 -changes. Please read the <uri link="/doc/en/gentoo-upgrading.xml">Gentoo
189 -Upgrading Guide</uri> to learn how to switch profiles.
190 -</note>
191 -
192 -</body>
193 -</section>
194 -<section>
195 -<title>Installing KDE as Split Packages</title>
196 -<body>
197 -
198 -<note>
199 -We recommend that you use the split packages to install KDE (rather than the
200 -monolithic packages, though both methods will be presented), as shown below.
201 -</note>
202 -
203 -<p>
204 -If you want to have more control on what parts of KDE you install, you have the
205 -possibility to install just the single KDE applications that you need. To know
206 -more about the ebuilds for the individual KDE programs see the <uri
207 -link="/doc/en/kde-split-ebuilds.xml">Split Ebuilds HOWTO</uri>.
208 -</p>
209 -
210 -<p>
211 -Knowing what to install and what not is a tad more difficult with split ebuilds.
212 -However, Gentoo does provide a few meta packages that will pull in a certain
213 -amount of KDE packages for you:
214 -</p>
215 -
216 -<ul>
217 - <li>
218 - If you want a full-blown KDE installation, install <c>kde-meta</c>.
219 - This package will pull in all KDE applications as dependencies.
220 - </li>
221 - <li>
222 - If you want a basic KDE installation, install <c>kdebase-startkde</c>. You
223 - can always install additional KDE applications when you want.
224 - </li>
225 - <li>
226 - If you want something in between <c>kde-meta</c> and
227 - <c>kdebase-startkde</c>, install <c>kdebase-meta</c>. This will install a
228 - few extra applications such as <c>konsole</c> and <c>kdm</c>.
229 - </li>
230 -</ul>
231 -
232 -<p>
233 -These three possibilities are the extreme limits; you are probably interested in
234 -a safe mixture of the two :) To make your decision process somewhat easier, the
235 -following table gives a short, very incomplete yet useful overview of some of
236 -the available KDE packages.
237 -</p>
238 -
239 -<p>
240 -These packages are <e>not</e> part of the <c>kdebase-startkde</c> installation.
241 -</p>
242 -
243 -<table>
244 -<tr>
245 - <th>Ebuild name</th>
246 - <th>Description</th>
247 -</tr>
248 -<tr>
249 - <ti><c>akregator</c></ti>
250 - <ti>
251 - The application to easily manage and browse internet RSS feeds.
252 - </ti>
253 -</tr>
254 -<tr>
255 - <ti><c>juk</c></ti>
256 - <ti>
257 - The playlist oriented media player, with a look and feel resembling Apple's
258 - iTunes.
259 - </ti>
260 -</tr>
261 -<tr>
262 - <ti><c>kate</c></ti>
263 - <ti>
264 - The <uri link="http://kate.kde.org/">KDE Advanced Text Editor</uri>, a
265 - multi-document editor with syntax highlighting, code folding and more.
266 - </ti>
267 -</tr>
268 -<tr>
269 - <ti><c>kmail</c></ti>
270 - <ti>
271 - Organize your e-mails efficiently with <uri
272 - link="http://kmail.kde.org/">KMail</uri>.
273 - </ti>
274 -</tr>
275 -<tr>
276 - <ti><c>knetattach</c></ti>
277 - <ti>
278 - With KNetAttach (also known as the <e>Network Folder Wizard</e>), you can
279 - easily add additional network folders to your KDE desktop.
280 - </ti>
281 -</tr>
282 -<tr>
283 - <ti><c>knode</c></ti>
284 - <ti>
285 - KNode is the powerful KDE newsreader.
286 - </ti>
287 -</tr>
288 -<tr>
289 - <ti><c>konsole</c></ti>
290 - <ti>
291 - <uri link="http://konsole.kde.org/">Konsole</uri> is the KDE terminal
292 - emulator.
293 - </ti>
294 -</tr>
295 -<tr>
296 - <ti><c>kontact</c></ti>
297 - <ti>
298 - <uri link="http://kontact.kde.org/">Kontact</uri> is the KDE Personal
299 - Information Manager, helping you manage your communications more easily,
300 - organize your work faster and work together more closely.
301 - </ti>
302 -</tr>
303 -<tr>
304 - <ti><c>kopete</c></ti>
305 - <ti>
306 - <uri link="http://kopete.kde.org/index.php">Kopete</uri> is KDE's Instant
307 - Messenger supporting all known IM protocols.
308 - </ti>
309 -</tr>
310 -<tr>
311 - <ti><c>korganizer</c></ti>
312 - <ti>
313 - <uri link="http://korganizer.kde.org/">Korganizer</uri> is the calendar and
314 - scheduling application for KDE.
315 - </ti>
316 -</tr>
317 -<tr>
318 - <ti><c>kpdf</c></ti>
319 - <ti>
320 - With <uri link="http://kpdf.kde.org/">KPDF</uri> you can view and work with
321 - PDF files. It has very unique features which enhance your viewing pleasure
322 - enormously.
323 - </ti>
324 -</tr>
325 -<tr>
326 - <ti><c>kscd</c></ti>
327 - <ti>
328 - kscd is a graphical CD player for KDE.
329 - </ti>
330 -</tr>
331 -<tr>
332 - <ti><c>ksnapshot</c></ti>
333 - <ti>
334 - With ksnapshot you can take screen shots from your desktop.
335 - </ti>
336 -</tr>
337 -<tr>
338 - <ti><c>kuickshow</c></ti>
339 - <ti>
340 - The KDE kuickshow application is able to browse amongst and display
341 - various image formats.
342 - </ti>
343 -</tr>
344 -</table>
345 -
346 -<p>
347 -And this is just the tip of the iceberg. If you want to know more about all
348 -possible KDE applications, take a look inside the <uri
349 -link="http://packages.gentoo.org/category/kde-base?full_cat">kde-base
350 -category</uri>. Their function should be available in the description.
351 -</p>
352 -
353 -<p>
354 -To preview what emerge would install, use <c>emerge -p</c> together with the
355 -<c>less</c> pager, otherwise you might not be able to see all packages.
356 -</p>
357 -
358 -<pre caption="Previewing the kde installation">
359 -<comment>(Substitute with your choice of package(s))</comment>
360 -# <i>emerge -p kdebase-startkde | less</i>
361 -</pre>
362 -
363 -<p>
364 -If you are happy with the proposed result, leave the <c>-p</c> out. This
365 -building process will take some time as KDE is a big environment. Don't be
366 -surprised when your system does not finish immediately.
367 -</p>
368 -
369 -</body>
370 -</section>
371 -<section>
372 -<title>Installing KDE as Monolithic Packages</title>
373 -<body>
374 -
375 -<p>
376 -Although the split ebuilds are the recommended way to install KDE, you do have
377 -the option of installing the monolithic ebuilds.
378 -</p>
379 -
380 -<p>
381 -The KDE project releases new versions of its desktop environment as a set of
382 -about 16 big packages, each containing many applications (thus they are called
383 -"monolithic"), so you need to decide which of these packages you want to
384 -install.
385 -</p>
386 -
387 -<p>
388 -If you want to see what it looks like to have all these packages installed,
389 -just check yourself:
390 -</p>
391 -
392 -<pre caption="Listing all packages KDE would install">
393 -# <i>emerge --pretend kde | less</i>
394 -</pre>
395 -
396 -<p>
397 -If you're not interested in installing all those packages, you can emerge them
398 -individually. You will most definitely want the <c>kdebase</c> package as it
399 -contains KDE's base packages and required dependencies. The following table
400 -lists some of the other available packages that you can install.
401 -</p>
402 -
403 -<table>
404 -<tr>
405 - <th>Package</th>
406 - <th>Description</th>
407 -</tr>
408 -<tr>
409 - <ti>kdeaccessibility</ti>
410 - <ti>
411 - Accessibility related programs, managed by the <uri
412 - link="http://accessibility.kde.org">KDE Accessibility Project</uri>
413 - </ti>
414 -</tr>
415 -<tr>
416 - <ti>kdeadmin</ti>
417 - <ti>
418 - KDE Administrative tools, such as <c>KCron</c> (Task Scheduling),
419 - <c>KUser</c> (User Management) and <c>KDat</c> (Backup Management).
420 - </ti>
421 -</tr>
422 -<tr>
423 - <ti>kdeartwork</ti>
424 - <ti>
425 - Various art-related stuff, including screen savers and themes. See also <uri
426 - link="http://www.kde-artists.org/">www.kde-artists.org</uri> for more KDE related
427 - artwork.
428 - </ti>
429 -</tr>
430 -<tr>
431 - <ti>kdeedu</ti>
432 - <ti>
433 - Educational KDE applications focused on school children aged 3 to 18. See
434 - also the <uri link="http://edu.kde.org">KDE Edu Project</uri>.
435 - </ti>
436 -</tr>
437 -<tr>
438 - <ti>kdegames</ti>
439 - <ti>
440 - Various KDE-developed games. More information can be found at the <uri
441 - link="http://games.kde.org">KDE Games Center</uri>.
442 - </ti>
443 -</tr>
444 -<tr>
445 - <ti>kdegraphics</ti>
446 - <ti>
447 - Graphic-related tools for KDE, including <c>KSnapshot</c> (Screenshot
448 - Software), <c>KolourPaint</c> (Simple Graphical Editor), <c>Kpdf</c>
449 - (PDF viewer), <c>KIconEdit</c> (Icon Editor) and <c>KPovModeler</c>
450 - (a 3D Modeler).
451 - </ti>
452 -</tr>
453 -<tr>
454 - <ti>kdemultimedia</ti>
455 - <ti>
456 - Multimedia-related applications, including support for CD, MP3, DVD,
457 - sequencing, sound and video applications. More information can be found on
458 - the <uri link="http://multimedia.kde.org">KDE Multimedia Project</uri>
459 - web site.
460 - </ti>
461 -</tr>
462 -<tr>
463 - <ti>kdenetwork</ti>
464 - <ti>
465 - Network-related applications such as <c>Kopete</c> (Multi-Protocol Instant
466 - Messaging), <c>kppp</c> (Dial-In) and <c>KSirc</c> (IRC client). Note that
467 - <c>konqueror</c> (File Manager <e>and</e> Browser) is part of <c>kdebase</c>!
468 - </ti>
469 -</tr>
470 -<tr>
471 - <ti>kdepim</ti>
472 - <ti>
473 - Personal Information Management tools, such as <c>KOrganizer</c> (Journal),
474 - <c>KAddressbook</c> (Address book), <c>Kontact</c> (Groupware) and
475 - <c>KMail</c> (E-mail). More information online at the <uri
476 - link="http://pim.kde.org">KDE PIM Project</uri> web site.
477 - </ti>
478 -</tr>
479 -<tr>
480 - <ti>kdesdk</ti>
481 - <ti>
482 - Code development tools, including <c>KBabel</c> (Translation tool),
483 - <c>KBugBuster</c> (Front end for KDE bug tracking) and <c>Kompare</c> (GUI
484 - to see differences between files).
485 - </ti>
486 -</tr>
487 -<tr>
488 - <ti>kdetoys</ti>
489 - <ti>
490 - Various toys to amuse yourself with when you're waiting for your pizza
491 - delivery. You'll find applets such as <c>eyesapplet</c> and
492 - <c>fifteenapplet</c>, but also nifty tools like <c>amor</c> which doesn't do
493 - much except eat resources :)
494 - </ti>
495 -</tr>
496 -<tr>
497 - <ti>kdeutils</ti>
498 - <ti>
499 - Graphical system tools such as <c>kcalc</c> (Calculator), <c>kdessh</c> (SSH
500 - terminal), <c>kfloppy</c> (Floppy-related actions), etc.
501 - </ti>
502 -</tr>
503 -<tr>
504 - <ti>kde-i18n</ti>
505 - <ti>
506 - Internationalization files for KDE. This includes translated
507 - documentation. See also the <uri link="http://i18n.kde.org">KDE i18n
508 - project</uri> for more information.
509 - </ti>
510 -</tr>
511 -</table>
512 -
513 -<p>
514 -For instance, to install KDE with only the network- and admin-related
515 -applications:
516 -</p>
517 -
518 -<pre caption="Example installation of individual KDE components">
519 -# <i>emerge kdebase kdenetwork kdeadmin</i>
520 -</pre>
521 -
522 -<p>
523 -In case you wonder: compiling KDE does take a while.
524 -</p>
525 -
526 -</body>
527 -</section>
528 -<section>
529 -<title>External KDE applications</title>
530 -<body>
531 -
532 -<p>
533 -The number of KDE applications is not limited to those shipped with the
534 -official KDE releases, but includes hundreds of other applications that use the
535 -KDE framework and libraries. Here we list just a few of the most popular ones.
536 -</p>
537 -
538 -<table>
539 -<tr>
540 - <th>Ebuild name</th>
541 - <th>Description</th>
542 -</tr>
543 -<tr>
544 - <ti><c>koffice</c></ti>
545 - <ti>
546 - <uri link="http://www.koffice.org/">KOffice</uri> is the comprehensive KDE
547 - office suite, featuring applications for word processing (KWord),
548 - spreadsheet calculations (KSpread), presentation (KPresenter), image
549 - manipulation (Krita), database management (Kexi) and much more.
550 - Just as KDE can be installed through the <c>kde</c> or <c>kde-meta</c>
551 - ebuilds, you can install KOffice as a single package (<c>koffice</c>) or as
552 - a set of individual packages (<c>koffice-meta</c>).
553 - </ti>
554 -</tr>
555 -<tr>
556 - <ti><c>amarok</c></ti>
557 - <ti>
558 - With <uri link="http://amarok.kde.org/">amaroK</uri> you have a powerful
559 - music player for Unix/Linux.
560 - </ti>
561 -</tr>
562 -<tr>
563 - <ti><c>k3b</c></ti>
564 - <ti>
565 - <uri link="http://www.k3b.org/">K3B</uri> is a complete CD/DVD burning
566 - utility with Audio support. Burning CDs was never this easy.
567 - </ti>
568 -</tr>
569 -<tr>
570 - <ti><c>kaffeine</c></ti>
571 - <ti>
572 - <uri link="http://kaffeine.sourceforge.net/">Kaffeine</uri> is a full
573 - featured multimedia-player for KDE.
574 - </ti>
575 -</tr>
576 -</table>
577 -
578 -</body>
579 -</section>
580 +<title>Moved</title>
581 <section>
582 -<title>First Impressions</title>
583 <body>
584
585 <p>
586 -Let us have a look at the result. Your mother has probably told you
587 -never to work as root. So we'll take your mother's advice and test
588 -KDE as a user. Log in as your user and configure your session so it starts KDE
589 -when you issue <c>startx</c>. You can do this by writing <c>exec startkde</c> in
590 -<path>~/.xinitrc</path> (see also
591 -<uri link="/doc/en/xorg-config.xml#using_startx">Using startx</uri> in the
592 -<uri link="/doc/en/xorg-config.xml">X Server Configuration Howto</uri>):
593 -</p>
594 -
595 -<pre caption="Configuring your local session">
596 -$ <i>echo "exec startkde" &gt; ~/.xinitrc</i>
597 -</pre>
598 -
599 -<p>
600 -Now start up your graphical environment by running <c>startx</c>.
601 -</p>
602 -
603 -<pre caption="Starting KDE">
604 -$ <i>startx</i>
605 -</pre>
606 -
607 -<p>
608 -You will be greeted by an application called <c>KPersonalizer</c>.
609 -Congratulations, let's now take a look at how we can configure KDE...
610 +This document was moved to <uri>/proj/en/desktop/kde/kde-config.xml</uri>
611 </p>
612
613 </body>
614 </section>
615 </chapter>
616 -<chapter>
617 -<title>Configuring KDE</title>
618 -<section>
619 -<title>KPersonalizer</title>
620 -<body>
621 -
622 -<p>
623 -KPersonalizer is the application that configures KDE for you. It's a very
624 -useful wizard that allows you to quickly change KDE to suit your own needs. When
625 -you run KDE for the first time, KPersonalizer is automatically started.
626 -</p>
627 -
628 -<p>
629 -The first input KPersonalizer requests is your country and the language of your
630 -choice. As we haven't installed the necessary language packs on your system yet,
631 -the available languages will be very slim -- you'll probably have only English
632 -to choose from. Don't mind this, we will change the language later on (if
633 -applicable of course).
634 -</p>
635 -
636 -<p>
637 -The second choice you're offered is the <e>System Behavior</e>. This includes
638 -window activation, mouse selection, etc. When you select a certain behavior
639 -its description is shown to help you choose the behavior you like. If you're
640 -uncertain, don't panic -- you are able to change the behavior whenever you
641 -want.
642 -</p>
643 -
644 -<p>
645 -Next, KPersonalizer asks for the amount of eye-candy it should activate. The
646 -more eye-candy you want, the funkier your KDE will be, but the more your CPU
647 -will be stressed. However, this should be taken with a bit of salt - on a 600
648 -Mhz CPU with 128 Mb of memory, enabling full eye-candy still results in a
649 -responsive system.
650 -</p>
651 -
652 -<p>
653 -Finally, KDE asks what style you want to use. A style defines the window
654 -decoration, theme, button layout, etc. Try several styles to see which one you
655 -like the most. Did we already mention KDE is fully configurable?
656 -</p>
657 -
658 -<p>
659 -Now sit back and enjoy -- KDE will start up and you'll be greeted by a nice,
660 -clean, functional desktop environment.
661 -</p>
662 -
663 -</body>
664 -</section>
665 -<section>
666 -<title>Installing Language Packs</title>
667 -<body>
668 -
669 -<p>
670 -If English isn't your native language or you're just interested in working with
671 -KDE in a foreign language, please read on. We will install the language pack(s)
672 -for the language(s) you want to use with KDE.
673 -</p>
674 -
675 -<p>
676 -Language packs are contained in the <c>kde-i18n</c> package. To install the
677 -language packs of your choice, you need to set the <c>LINGUAS</c> variable to
678 -the language(s) you want to use. It is advisable to set this variable in
679 -<path>/etc/make.conf</path> so that updating your system doesn't remove the
680 -language packs you want.
681 -</p>
682 -
683 -<pre caption="Setting LINGUAS in /etc/make.conf">
684 -# <i>nano -w /etc/make.conf</i>
685 -<comment>(As an example, we install the language packs for Dutch (nl)
686 - and French (fr))</comment>
687 -LINGUAS="nl fr"
688 -</pre>
689 -
690 -<p>
691 -Now run <c>emerge kde-i18n</c> to install the language packs. Once settled, fire
692 -up KDE, then start the KDE Control Center (K-menu &gt; Control Center). This is
693 -<e>the</e> application where you can control almost every aspect of KDE. It is
694 -much more extended than KPersonalizer.
695 -</p>
696 -
697 -<p>
698 -To change your language, go to <c>Regional &amp; Accessibility</c>,
699 -<c>Country/Region &amp; Languages</c>. Then add the language(s) of your choice.
700 -To see your (localized) KDE in its full glory, log out and in again, and enjoy.
701 -</p>
702 -
703 -</body>
704 -</section>
705 -<section>
706 -<title>Graphical Login</title>
707 -<body>
708 -
709 -<p>
710 -If you want to use <c>kdm</c> as graphical login manager (which means you don't
711 -have to login to a terminal and type <c>startx</c> every time) you need to
712 -first emerge it, and then edit a configuration file and set up your system so
713 -that it enters graphical mode after boot, as explained below.
714 -</p>
715 -
716 -<note>
717 -It's possible that you already have <c>kdm</c> installed for various reasons.
718 -If you get an error with packages blocking <c>kde-base/kdm</c>, proceed with
719 -the next section.
720 -</note>
721 -
722 -<pre caption="Installing kdm">
723 -# <i>emerge --ask kdm</i>
724 -</pre>
725 -
726 -<p>
727 -In <path>/etc/conf.d/xdm</path>, set the <c>DISPLAYMANAGER</c> variable to
728 -<c>kdm</c>.
729 -</p>
730 -
731 -<pre caption="Setting DISPLAYMANAGER in /etc/conf.d/xdm">
732 -# <i>nano -w /etc/conf.d/xdm</i>
733 -<comment>(Edit the following variable)</comment>
734 -DISPLAYMANAGER="kdm"
735 -</pre>
736 -
737 -<p>
738 -Finish up by adding <c>xdm</c> to the default runlevel:
739 -</p>
740 -
741 -<pre caption="Adding xdm to the default runlevel">
742 -# <i>rc-update add xdm default</i>
743 -</pre>
744 -
745 -<p>
746 -When you reboot your system, it will use KDM as the graphical login manager.
747 -</p>
748 -
749 -<p>
750 -KDM will provide a list of available sessions to choose from, including KDE -
751 -of course - and including all the other sessions installed on your system,
752 -which KDM finds by looking in <path>/usr/share/xsessions/</path>. Thus, if you
753 -use KDM, you don't need to edit <path>~/.xinitrc</path>.
754 -</p>
755 -
756 -</body>
757 -</section>
758 -<section id="kde_device_mounting">
759 -<title>Setup KDE to Mount Devices</title>
760 -<body>
761 -
762 -<!-- TODO add pmount package when pmount is in arch.
763 - Also, add pmount to the default runlevel -->
764 -
765 -<p>
766 -KDE gives you the power to mount devices such as CDROMs or USB sticks through a
767 -single click in a graphical interface. To accomplish this goal you need to have
768 -KDE compiled with <c>hal</c> in your USE variable and to have <c>dbus</c> and
769 -<c>hal</c> installed on your system. You should also add <c>dbus</c> and
770 -<c>hal</c> to the default runlevel and add yourself to the <c>plugdev</c>
771 -group.
772 -</p>
773 -
774 -<pre caption="Setup device mounting">
775 -# <i>emerge --ask dbus hal</i>
776 -# <i>rc-update add dbus default</i>
777 -# <i>rc-update add hald default</i>
778 -<comment>Add &lt;user&gt; to the plugdev group</comment>
779 -# <i>gpasswd -a &lt;user&gt; plugdev</i>
780 -</pre>
781 -
782 -</body>
783 -</section>
784 -</chapter>
785 -<chapter>
786 -<title>Managing KDE Installations</title>
787 -<section>
788 -<title>Multiple Installations</title>
789 -<body>
790 -
791 -<p>
792 -One peculiarity of the way KDE is managed in Gentoo is that when a new series
793 -of KDE appears (such as the 3.5.x series, which supersedes the 3.4.x series)
794 -it will be installed alongside the old one and will not overwrite it. So if
795 -for instance you had KDE 3.4 already installed and you emerge KDE 3.5,
796 -you will have two versions, one installed in <path>/usr/kde/3.4/</path> and
797 -the other in <path>/usr/kde/3.5/</path>.
798 -</p>
799 -
800 -<p>
801 -It should be noted that your settings for different KDE installations will be
802 -kept separate in the home directory. KDE 3.4 reads its settings from the
803 -directory <path>/home/&lt;user&gt;/.kde3.4</path>, and the first time you run
804 -KDE 3.5 a directory named <path>/home/&lt;user&gt;/.kde3.5</path> will be
805 -created by migrating the settings in the 3.4 directory and will be then used to
806 -store preferences and data.
807 -</p>
808 -
809 -<p>
810 -Another important remark to keep in mind when upgrading your KDE installation
811 -is that you could have problems with the external KDE applications you have
812 -installed (such as <c>koffice</c>, <c>amarok</c> or <c>k3b</c>) until you
813 -recompile them against the new KDE version. So as soon as you start using the
814 -new KDE you should reemerge them to make them link against the new libraries.
815 -</p>
816 -
817 -</body>
818 -</section>
819 -<section>
820 -<title>Unmerging Old Versions</title>
821 -<body>
822 -
823 -<p>
824 -Having multiple versions of KDE installed poses the problem of how to remove
825 -the old ones when we decide that they are not needed anymore. Unfortunately
826 -portage does not support unmerging a package with all its dependencies with a
827 -single command, so if for instance you run <c>emerge --unmerge kde</c> you will
828 -not remove the actual kde packages.
829 -</p>
830 -
831 -<p>
832 -To remove a KDE installation (e.g. KDE 3.4), the single packages have to be
833 -removed.
834 -</p>
835 -
836 -<pre caption="Removing KDE 3.4 packages">
837 -# <i>emerge --unmerge =arts-3.4* =kdelibs-3.4* =kdebase-3.4* ...</i>
838 -</pre>
839 -
840 -<p>
841 -Obviously this is very frustrating if you have many KDE packages installed.
842 -However this operation can be automated in many ways. The following one is
843 -an example.
844 -</p>
845 -
846 -<p>
847 -First we list all the packages that we want to remove. We use the <c>equery</c>
848 -command for this, part of the <c>app-portage/gentoolkit</c> package:
849 -</p>
850 -
851 -<pre caption="Listing packages to remove">
852 -<comment>(List all the installed KDE packages)</comment>
853 -# <i>equery list kde-base/</i>
854 -<comment>(List all the installed KDE packages and select the ones from KDE 3.4)</comment>
855 -# <i>equery list kde-base/ | grep 3\.4</i>
856 -</pre>
857 -
858 -<p>
859 -At this point you should double-check that the list corresponds to the packages
860 -that should be removed from the system. If you think it is ok, you can go on
861 -and pass the list to the <c>emerge --unmerge</c> command.
862 -</p>
863 -
864 -<pre caption="Removing selected packages">
865 -# <i>equery list kde-base/ | grep 3\.4 | xargs emerge --unmerge --pretend</i>
866 -</pre>
867 -
868 -<p>
869 -Check again the output and reissue the command without <c>--pretend</c> to
870 -start the unmerging process.
871 -</p>
872 -
873 -<p>
874 -After the job has completed, the directory <path>/usr/kde/3.4/</path> should
875 -contain only a few files (mainly configuration files, portage has a policy to
876 -never touch configurations). If you desire, you can safely wipe out
877 -<path>/usr/kde/3.4/</path> with its content to remove what remains of KDE 3.4.
878 -</p>
879 -
880 -</body>
881 -</section>
882 -</chapter>
883 -<chapter>
884 -<title>Frequently Asked Questions</title>
885 -<section>
886 -<title>KDE is extremely slow during startup</title>
887 -<body>
888 -
889 -<p>
890 -Make sure your <path>/etc/hosts</path> file is correct:
891 -</p>
892 -
893 -<ul>
894 - <li>
895 - If you have a static IP address, make sure your FQDN and hostname are
896 - mentioned on that line, like <c>192.168.0.10 tux.mydomain tux</c>
897 - </li>
898 - <li>
899 - If you have a dynamic IP address or you do not have any additional
900 - interfaces at all, add your hostname after the localhost statement, like
901 - <c>127.0.0.1 localhost tux</c>
902 - </li>
903 -</ul>
904 -
905 -<p>
906 -Check if you have DMA enabled for your disks:
907 -</p>
908 -
909 -<pre caption="Verifying DMA settings">
910 -# <i>hdparm /dev/hda</i>
911 -<comment>(...)</comment>
912 -using_dma = 1 (on)
913 -<comment>(...)</comment>
914 -</pre>
915 -
916 -</body>
917 -</section>
918 -</chapter>
919 -
920 </guide>
921
922
923
924 1.16 xml/htdocs/doc/en/kde-split-ebuilds.xml
925
926 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.16&view=markup
927 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.16&content-type=text/plain
928 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?r1=1.15&r2=1.16
929
930 Index: kde-split-ebuilds.xml
931 ===================================================================
932 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
933 retrieving revision 1.15
934 retrieving revision 1.16
935 diff -u -r1.15 -r1.16
936 --- kde-split-ebuilds.xml 17 Jan 2008 00:14:40 -0000 1.15
937 +++ kde-split-ebuilds.xml 26 Apr 2008 19:21:00 -0000 1.16
938 @@ -1,10 +1,10 @@
939 <?xml version='1.0' encoding='UTF-8'?>
940
941 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.15 2008/01/17 00:14:40 jkt Exp $ -->
942 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.16 2008/04/26 19:21:00 neysx Exp $ -->
943
944 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
945
946 -<guide link="/doc/en/kde-split-ebuilds.xml">
947 +<guide redirect="/proj/en/desktop/kde/kde-split-ebuilds.xml">
948
949 <title>The KDE Split Ebuilds HOWTO</title>
950
951 @@ -25,437 +25,16 @@
952 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
953 <license/>
954
955 -<version>1.11</version>
956 -<date>2008-01-16</date>
957 +<version>2</version>
958 +<date>2008-04-26</date>
959
960 <chapter>
961 -<title>The Split KDE Ebuilds</title>
962 +<title>Moved</title>
963 <section>
964 -<title>What they are</title>
965 <body>
966
967 <p>
968 -Until January 2005, the only KDE ebuilds in Portage were 'monolithic' ones.
969 -That is to say, there were only 15 ebuilds (<c>kdebase</c>, <c>kdenetwork</c>,
970 -...), and each one installed many applications that did not, in fact, depend on
971 -one another. This was clearly a suboptimal situation, and not very Gentoo-ish,
972 -but it was tolerated for a long time.
973 -</p>
974 -
975 -<p>
976 -The new 'split' ebuilds (for <c>konqueror</c>, <c>kmail</c>, ...) rectified the
977 -situation by providing separate ebuilds for all the separate KDE applications.
978 -This gave us a grand total of about 330 new ebuilds in the kde-base category.
979 -</p>
980 -
981 -<p>
982 -We still provide monolithic ebuilds for 3.5 and they are cleanly interoperable
983 -with the split ones. However, the split ebuilds are the new default, and there
984 -will be no monolithic ebuilds after KDE 4.0.
985 -</p>
986 -
987 -<p>
988 -Finally, it should be mentioned that there are split ebuilds for Koffice as
989 -well. These provide <c>kword</c>, <c>kugar</c>, etc. as separate packages.
990 -</p>
991 -
992 -</body>
993 -</section>
994 -<section>
995 -<title>How to install the split ebuilds</title>
996 -<body>
997 -
998 -<p>
999 -The latest stable KDE release, as of this writing, is 3.5.7. The latest
1000 -unstable (~arch) is 3.5.8. Split and monolithic ebuilds for both releases are
1001 -present in Portage. The 4.0.0 release is about to enter the tree in hardmasked
1002 -state.
1003 -</p>
1004 -
1005 -<ul>
1006 - <li>
1007 - To emerge a particular package, such as kmail, simply <c>emerge
1008 - kmail</c>.
1009 - </li>
1010 - <li>
1011 - To emerge the basic KDE environment allowing you to login into a
1012 - minimalistic KDE session, <c>emerge kdebase-startkde</c>.
1013 - </li>
1014 - <li>
1015 - Finally, for the exact equivalent of one of the monolithic packages - for
1016 - instance, to get all the applications included in <c>kdebase</c> using
1017 - split ebuilds - you can <c>emerge kdebase-meta</c> (or <c>kdepim-meta</c>,
1018 - etc.) To get absolutely all KDE split ebuilds, <c>emerge kde-meta</c>.
1019 - </li>
1020 -</ul>
1021 -
1022 -</body>
1023 -</section>
1024 -<section>
1025 -<title>How to upgrade from the monolithic to the split ebuilds</title>
1026 -<body>
1027 -
1028 -<p>
1029 -If you have KDE 3.3.x installed, you can simply <c>emerge kde-meta</c> to
1030 -install the 3.5.x split ebuilds without disturbing your existing installation.
1031 -</p>
1032 -
1033 -<p>
1034 -If you have the KDE 3.4.x or 3.5.x monolithic ebuilds installed, you must
1035 -unmerge them before emerging the split ebuilds. However, this process can be
1036 -done for each monolithic ebuild in turn; you don't have to unmerge all of KDE
1037 -at once.
1038 -</p>
1039 -
1040 -<p>
1041 -If you're in doubt, remember there are blocking dependencies in place between
1042 -each monolithic ebuild and the split ebuilds derived from it. Portage won't
1043 -allow an illegal state to be created, so any emerge or unmerge it allows is
1044 -OK.
1045 -</p>
1046 -
1047 -</body>
1048 -</section>
1049 -<section>
1050 -<title>Advantages of the split ebuilds</title>
1051 -<body>
1052 -
1053 -<p>
1054 -Here's a brief list of what we gain from switching to the split ebuilds:
1055 -</p>
1056 -
1057 -<ul>
1058 - <li>
1059 - Most KDE packages aren't changed at all between minor KDE releases. For
1060 - example, the update from 3.3.1 to 3.3.2 changed fewer than 100 packages out
1061 - of 320. Split packages allow us to create new ebuilds only for the packages
1062 - that are actually changed, saving (in this example) more than two-thirds of
1063 - the compilation time on an upgrade.
1064 - </li>
1065 - <li>
1066 - Patches usually affect a specific package. With split ebuilds, they can be
1067 - tested, approved and committed faster, and the developers have less to do;
1068 - and, as above, the user will spend less time upgrading. This is especially
1069 - important for security updates.
1070 - </li>
1071 - <li>
1072 - Users of other desktops and leaner WMs can emerge a few KDE apps they like
1073 - without the (quite big) overhead of the rest of, say, <c>kdebase</c> or
1074 - <c>kdepim</c>.
1075 - </li>
1076 - <li>
1077 - Users can fine-tune the packages they have installed. Reasons you might
1078 - want this include:
1079 -
1080 - <ul>
1081 - <li>
1082 - You care about compilation time. <c>emerge kdebase kdepim
1083 - kdenetwork</c> takes far too long when what you really need is
1084 - <c>konqueror</c>, <c>kmail</c> and <c>kopete</c>. Besides, CPU time is
1085 - money... somewhere.
1086 - </li>
1087 - <li>
1088 - You care about disk usage. Every unused package is that many megabytes
1089 - blocking the pores between your disk's sectors. A disk with more free
1090 - space breathes freely; it's a fast, happy disk.
1091 - </li>
1092 - <li>
1093 - You care about system security. All installed software is a potential
1094 - source of vulnerabilities, and there's no excuse for unused software
1095 - left lying around.
1096 - </li>
1097 - <li>
1098 - You faithfully adhere to the <uri link="/main/en/philosophy.xml">Gentoo
1099 - Way</uri>, and can't stand packages being bundled together and forced
1100 - on the user. (Neither could we.)
1101 - </li>
1102 - </ul>
1103 - </li>
1104 - <li>
1105 - Finally, the split ebuilds also allow more compile-time flexibility with
1106 - USE flags.
1107 - </li>
1108 -</ul>
1109 -
1110 -</body>
1111 -</section>
1112 -<section>
1113 -<title>Split and monolithic ebuild interoperability</title>
1114 -<body>
1115 -
1116 -<p>
1117 -Split and monolithic ebuilds can be mixed freely. The only restriction is that
1118 -a monolithic ebuild can't be installed at the same time as a split ebuild
1119 -deriving from it. There are blocking dependencies in the ebuilds that enforce
1120 -this, so you can do anything emerge allows you to do.
1121 -</p>
1122 -
1123 -<p>
1124 -Ordinarily, however, there's no reason to use such a mixed configuration. In
1125 -fact, except for special cases like very slow-compiling boxes (mips), you should
1126 -use the split ebuilds for all your needs.
1127 -</p>
1128 -
1129 -<p>
1130 -The split ebuilds are also the default ebuilds. This means that when some other
1131 -ebuild depends on a KDE application, it will want to install a split ebuild.
1132 -However, the matching monolithic ebuild will also satisfy that dependency, so
1133 -you can emerge the monolithic ebuild manually and then emerge the ebuild that
1134 -depended on it.
1135 -</p>
1136 -
1137 -</body>
1138 -</section>
1139 -</chapter>
1140 -
1141 -<chapter>
1142 -<title>Performance issues</title>
1143 -<section>
1144 -<title>Why split ebuilds are slow</title>
1145 -<body>
1146 -
1147 -<p>
1148 -It's been <uri link="http://bugs.gentoo.org/show_bug.cgi?id=11123">said</uri>
1149 -before that split ebuilds would take much more time to emerge than the
1150 -monolithic ones, due to the overhead of unpacking and running configure for
1151 -every package. A complete <c>emerge kde-meta</c> could take 20-30% longer
1152 -than a classic <c>emerge kde</c>, unacceptable in an already long compile.
1153 -</p>
1154 -
1155 -<p>
1156 -Moreover, at present the split ebuilds always run <c>make -f
1157 -admin/Makefile.cvs</c> (this means running autoconf, automake, etc. and several
1158 -related kde-specific scripts). This adds an additional slowdown of
1159 -approximately the same order as a configure run.
1160 -</p>
1161 -
1162 -<p>
1163 -Finally, a split ebuild needs to extract specific files out of a large tarball.
1164 -This is slower than extracting a dedicated, small tarball. However, creating
1165 -such small tarballs for the autotools-based build system of KDE 3.x is
1166 -difficult.
1167 -</p>
1168 -
1169 -<p>
1170 -It is worth reiterating here that with the split ebuilds a KDE upgrade's
1171 -compilation time can be greatly reduced by only upgrading the packages that
1172 -actually changed. The benefit from a single such update often overshadows the
1173 -overhead incurred during the original installation.
1174 -</p>
1175 -
1176 -<p>
1177 -Finally, installing all of KDE makes sense if you want to explore the available
1178 -packages or are setting up a multi-user environment; however, most people use
1179 -only some of the 300+ KDE apps available. Anyone who really cares about
1180 -compilation time, such as owners of older boxes, can gain more time by
1181 -selectively installing packages than they might lose by the overhead incurred.
1182 -</p>
1183 -
1184 -</body>
1185 -</section>
1186 -<section>
1187 -<title>How split ebuilds will be made faster</title>
1188 -<body>
1189 -
1190 -<p>
1191 -Most or even all of the split ebuilds' performance issues are tied to autotools
1192 -- autoconf, automake and other tools which manage the <c>./configure;make;make
1193 -install</c> build system used in KDE 3.x.
1194 -</p>
1195 -
1196 -<p>
1197 -KDE 4 will (as far as we can tell now) adopt a completely new build system,
1198 -which among other things will greatly reduce the time its equivalent of a
1199 -<c>make -f admin/Makefile.common; ./configure</c> will take. Hopefully, it will
1200 -also make it much easier to create a small tarball for each split ebuild by
1201 -lowering the cost of generating its equivalent of configure scripts (if any).
1202 -</p>
1203 -
1204 -</body>
1205 -</section>
1206 -</chapter>
1207 -
1208 -<chapter>
1209 -<title>Split ebuilds FAQ</title>
1210 -<section>
1211 -<title>Why are some split packages missing the newest ebuild versions?</title>
1212 -<body>
1213 -
1214 -<p>
1215 -As explained above, not all applications are really updated between minor KDE
1216 -releases, and so not all applications receive new ebuild versions. For
1217 -instance, libkdenetwork wasn't updated in 3.5.0_beta2, so the latest ebuild
1218 -available with that release was 3.5_beta1.
1219 -</p>
1220 -
1221 -<p>
1222 -This is done purely to reduce compilation time during an upgrade. If we had
1223 -made a libkdenetwork-3.5.0_beta2 ebuild, it would have installed precisely the
1224 -same files as the 3.5_beta1 ebuild. The various dependencies are updated to
1225 -work correctly (i.e. no ebuild will depend on libkdenetwork-3.5.0_beta2).
1226 -</p>
1227 -
1228 -</body>
1229 -</section>
1230 -<section>
1231 -<title>Can't we do this already with DO_NOT_COMPILE?</title>
1232 -<body>
1233 -
1234 -<p>
1235 -DO_NOT_COMPILE is an environment variable internal to the KDE build system. It
1236 -allows selectively disabling subdirectories from compilation. Some people used
1237 -to use it to compile subsets of the monolithic KDE ebuilds. For instance,
1238 -running <c>DO_NOT_COMPILE=konqueror emerge kdebase</c> would install a kdebase
1239 -without the <c>konqueror</c> application.
1240 -</p>
1241 -
1242 -<p>
1243 -However, DO_NOT_COMPILE was never intended to be used to interfere with the
1244 -operation of a package manager's automated builds. It does not work, it can
1245 -break your system, and it was never supported. We request everyone to refrain
1246 -from using it.
1247 -</p>
1248 -
1249 -<p>
1250 -Here is a partial list of the problems with DO_NOT_COMPILE:
1251 -</p>
1252 -
1253 -<ul>
1254 - <li>
1255 - It completely breaks Portage's dependency tracking. Portage does not know
1256 - about DO_NOT_COMPILE, and thinks the entire monolithic package has been
1257 - installed and can satisfy other packages' deps. This can cause other
1258 - packages not to emerge or not to run.
1259 - </li>
1260 - <li>
1261 - It forces the user to know the names and meanings of all the different
1262 - existing subdirs of the KDE modules. Very few users do know this, unless
1263 - they're KDE developers, so they can't use DO_NOT_COMPILE properly.
1264 - </li>
1265 - <li>
1266 - KDE module subdirs can have interdependencies between them, require a
1267 - particular build order, require another dir to be present even if it does
1268 - not have to be installed, and so forth. We put a lot of work into the split
1269 - ebuilds to make them work properly in this regard. DO_NOT_COMPILE is not
1270 - nearly a fine enough tool to achieve the same results, even given
1271 - sufficient knowledge on the user's part. The only thing you can do with it
1272 - is disable a few applications from compiling. It is practically impossible
1273 - to use it to install only a few selected applications from modules like
1274 - <c>kdebase</c> or <c>kdepim</c>.
1275 - </li>
1276 - <li>
1277 - If I installed kmail yesterday and want to add korn today, using
1278 - DO_NOT_COMPILE, it entails recompiling kmail as well. This means
1279 - DO_NOT_COMPILE is always much slower than split ebuilds.
1280 - </li>
1281 - <li>
1282 - DO_NOT_COMPILE can't be used to make precompiled packages (such as the GRP)
1283 - containing individual KDE apps.
1284 - </li>
1285 -</ul>
1286 -
1287 -</body>
1288 -</section>
1289 -<section>
1290 -<title>Aren't you putting too big a load on the Gentoo KDE maintainers?</title>
1291 -<body>
1292 -
1293 -<p>
1294 -Surprisingly, this question gets asked a lot. I'm glad users are so
1295 -considerate of us maintainers. Let me take this opportunity to assure you that
1296 -we're taking on the split ebuilds of our own free will; that we believe we'll
1297 -be able to continue maintaining them well; and that there's no chance of
1298 -talking us out of it :-)
1299 -</p>
1300 -
1301 -<p>
1302 -For completeness' sake, I should mention that maintainers from other archs
1303 -have in fact complained about the increased workload of testing and keywording
1304 -so many separate ebuilds. We're working to resolve this and it's a major reason
1305 -why monolithic ebuilds are in fact still available for KDE 3.5.
1306 -</p>
1307 -
1308 -</body>
1309 -</section>
1310 -<section>
1311 -<title>Are you going to remove the old-style (monolithic) ebuilds?</title>
1312 -<body>
1313 -
1314 -<p>
1315 -We intend to do so eventually. However, there will be both monolithic and split
1316 -ebuilds for all the KDE 3.x releases.
1317 -</p>
1318 -
1319 -<p>
1320 -If you prefer the monolithic ebuilds over the split ones, please
1321 -<uri link="http://bugs.gentoo.org">tell us</uri> your reasons.
1322 -</p>
1323 -
1324 -</body>
1325 -</section>
1326 -<section>
1327 -<title>There are too many ebuilds! How am I going to find the one I need?</title>
1328 -<body>
1329 -
1330 -<p>
1331 -Well, first of all, if you know the package you're looking for came with
1332 -kdebase, you can still <c>emerge kdebase-meta</c>, with much the same results
1333 -as if you emerged the monolithic <c>kdebase</c>. So, things haven't actually
1334 -become any worse due to the split ebuilds.
1335 -</p>
1336 -
1337 -<p>
1338 -Of course, all the usual ways of locating a package also apply. How would you
1339 -find your ebuild if it was a Gnome application? As a minimum, you do have to
1340 -know the name of the application you're looking for.
1341 -</p>
1342 -
1343 -<p>
1344 -The situation could, perhaps, be improved by introducing some more -meta
1345 -ebuilds. They are merely lists of dependencies, so they don't cost us anything.
1346 -This hasn't been decided yet. Also, it would be nice to have Portage sets
1347 -functionality before we do this extensively.
1348 -</p>
1349 -
1350 -</body>
1351 -</section>
1352 -<section>
1353 -<title>How can I list/unmerge all split ebuilds derived from a given package?</title>
1354 -<body>
1355 -
1356 -<p>
1357 -The objective here is to list all split kde ebuilds derived from, say, the
1358 -<c>kdebase</c> monolithic ebuild. Once again, the proper implementation (such as <uri
1359 -link="/proj/en/glep/glep-0021.html">GLEP 21</uri>) would make this trivial.
1360 -Today, however, you must become involved in the KDE eclasses' implementation
1361 -details to some degree. So, if you use any of these approaches in a script
1362 -that's not for private use, tell us about it.
1363 -</p>
1364 -
1365 -<p>
1366 -kde-functions.eclass defines functions called get-parent-package() and
1367 -get-child-packages() which do the translation for you. These two functions are
1368 -the correct way to accomplish this task from an ebuild or an external bash
1369 -script. Here is an example:
1370 -</p>
1371 -
1372 -<pre caption="Example usage of the kde-functions functions">
1373 -$ <i>function die() { echo $@; }</i> <comment># called to report errors</comment>
1374 -$ <i>source /usr/portage/eclass/kde-functions.eclass</i>
1375 -$ <i>get-parent-package konqueror</i> <comment># won't work, you must specify full name</comment>
1376 -Package konqueror not found in KDE_DERIVATION_MAP, please report bug <comment># error printed</comment>
1377 -$ <i>get-parent-package kde-base/konqueror</i> <comment># fully qualified package name</comment>
1378 -kde-base/kdebase <comment># result printed</comment>
1379 -$ <i>get-child-packages kde-base/kdebase</i>
1380 -<comment>(Long list of packages printed here)</comment>
1381 -</pre>
1382 -
1383 -<p>
1384 -If your script isn't in bash, you can grep kde-functions.eclass to extract the
1385 -(multiline) definition of the variable KDE_DERIVATION_MAP, which the
1386 -aforementioned functions use. This variable contains a whitespace-separated
1387 -list of words, and each two consecutive words map a parent package to a child
1388 -split ebuild.
1389 +This document was moved to <uri>/proj/en/desktop/kde/kde-split-ebuilds.xml</uri>
1390 </p>
1391
1392 </body>
1393
1394
1395
1396 --
1397 gentoo-doc-cvs@l.g.o mailing list