* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2005-09-09 7:26 Shyam Mani
0 siblings, 0 replies; 8+ messages in thread
From: Shyam Mani @ 2005-09-09 7:26 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/09/09 07:26:39
Modified: xml/htdocs/doc/en kde-split-ebuilds.xml
Log:
#103492 - Minor grammatical fixes, thanks to Erik Musick for reporting.
Revision Changes Path
1.7 +5 -5 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.7&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.7&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml.diff?r1=1.6&r2=1.7&cvsroot=gentoo
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- kde-split-ebuilds.xml 2 Jul 2005 12:31:47 -0000 1.6
+++ kde-split-ebuilds.xml 9 Sep 2005 07:26:39 -0000 1.7
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.6 2005/07/02 12:31:47 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.7 2005/09/09 07:26:39 fox2mike Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,7 +19,7 @@
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
<version>1.5</version>
@@ -271,7 +271,7 @@
<p>
The previous section listed methods of improving the performance of the
-split ebuilds specifically. Next we will briefly mention some future speedups
+split ebuilds specifically. Next, we will briefly mention some future speedups
which are equally applicable to the monolithic ebuilds. Such speedups help
make the split ebuilds 'fast enough', apart from comparisons with less
featureful solutions such as the monolithic ebuilds.
@@ -388,7 +388,7 @@
<body>
<p>
-We intend to so eventually. However, there will be both monolithic and split
+We intend to do so eventually. However, there will be both monolithic and split
ebuilds for all the KDE 3.4 releases.
</p>
@@ -406,7 +406,7 @@
<p>
Well, first of all, if you know the package you're looking for came with
kdebase, you can still <c>emerge kdebase-meta</c>, with much the same results
-as if you emerged the monolithic <c>kdebase</c>. So things haven't actually
+as if you emerged the monolithic <c>kdebase</c>. So, things haven't actually
become any worse due to the split ebuilds.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2005-10-30 18:26 Stefano Rossi
0 siblings, 0 replies; 8+ messages in thread
From: Stefano Rossi @ 2005-10-30 18:26 UTC (permalink / raw
To: gentoo-doc-cvs
so 05/10/30 18:26:17
Modified: xml/htdocs/doc/en kde-split-ebuilds.xml
Log:
#110460 updated KDE split ebuilds
Revision Changes Path
1.8 +61 -65 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- kde-split-ebuilds.xml 9 Sep 2005 07:26:39 -0000 1.7
+++ kde-split-ebuilds.xml 30 Oct 2005 18:26:17 -0000 1.8
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.7 2005/09/09 07:26:39 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.8 2005/10/30 18:26:17 so Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -22,8 +22,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.5</version>
-<date>2005-07-02</date>
+<version>1.6</version>
+<date>2005-10-30</date>
<chapter>
<title>The Split KDE Ebuilds</title>
@@ -32,20 +32,21 @@
<body>
<p>
-Until January 2005, the only KDE ebuilds in Portage were 'monolithic' ones. That
-is to say, there were only 15 ebuilds, and each one installed many applications
-that did not, in fact, depend on one another. This was clearly a suboptimal
-situation, and not very Gentoo-ish, but it was tolerated for a long time.
+Until January 2005, the only KDE ebuilds in Portage were 'monolithic' ones.
+That is to say, there were only 15 ebuilds (kdebase, kdenetwork, ...), and
+each one installed many applications that did not, in fact, depend on one
+another. This was clearly a suboptimal situation, and not very Gentoo-ish,
+but it was tolerated for a long time.
</p>
<p>
-The new 'split' ebuilds rectified the situation by providing separate ebuilds
-for all the separate KDE applications. This gave us a grand total of about 330
-new ebuilds in the kde-base category.
+The new 'split' ebuilds (for konqueror, kmail, ...) rectified the situation by
+providing separate ebuilds for all the separate KDE applications. This gave us
+a grand total of about 330 new ebuilds in the kde-base category.
</p>
<p>
-We still provide monolithic ebuilds for KDE 3.4 and they are cleanly
+We still provide monolithic ebuilds for KDE 3.4 and 3.5 and they are cleanly
interoperable with the split ones. However, the split ebuilds are the new
default, and there will be no monolithic ebuilds for KDE 4.0.
</p>
@@ -62,8 +63,9 @@
<body>
<p>
-The latest KDE release, as of this writing, is 3.4.1, recently marked stable.
-Both split and monolithic ebuilds for it are present in Portage.
+The latest stable KDE release, as of this writing, is 3.4.3. The latest
+unstable (package.masked) is 3.5.0_beta2. Split and monolithic ebuilds for both
+releases are present in Portage.
</p>
<ul>
@@ -92,6 +94,7 @@
<p>
If you have KDE 3.3.x installed, you can simply <c>emerge kde-meta</c> to
install the 3.4.x split ebuilds without disturbing your existing installation.
+The same applies to 3.5.x.
</p>
<p>
@@ -162,7 +165,7 @@
</ul>
</li>
<li>
- Finally, the split ebuilds also allow more compile-time flexibility with
+ Finally, the split ebuilds also allow more compile-time flexibility with
USE flags.
</li>
</ul>
@@ -208,8 +211,8 @@
It's been <uri link="http://bugs.gentoo.org/show_bug.cgi?id=11123">said</uri>
before that split ebuilds would take much more time to emerge than the
monolithic ones, due to the overhead of unpacking and running configure for
-every package. A complete <c>emerge kde-meta</c> could take 20-30% longer than a
-classic <c>emerge kde</c>, unacceptable in an already long compile.
+every package. A complete <c>emerge kde-meta</c> could take 20-30% longer
+than a classic <c>emerge kde</c>, unacceptable in an already long compile.
</p>
<p>
@@ -220,22 +223,23 @@
</p>
<p>
-On the face of it, this analysis looks bleak. However, several factors which
-offset this slowdown will be detailed in the next sections.
+Finally, a split ebuild needs to extract specific files out of a large tarball.
+This is slower than extracting a dedicated, small tarball. However, creating
+such small tarballs for the autotools-based build system of KDE 3.x is
+difficult.
</p>
<p>
It is worth reiterating here that with the split ebuilds a KDE upgrade's
-compilation time can be cut by half - and in some cases by a factor of ten or
-more - by only upgrading the packages that actually changed. The benefit from a
-single such update often overshadows the overhead incurred during the original
-installation.
+compilation time can be greatly reduced by only upgrading the packages that
+actually changed. The benefit from a single such update often overshadows the
+overhead incurred during the original installation.
</p>
<p>
Finally, installing all of KDE makes sense if you want to explore the available
-packages or are setting up a multi-user environment; however, most people
-use only some of the 300+ KDE apps available. Anyone who really cares about
+packages or are setting up a multi-user environment; however, most people use
+only some of the 300+ KDE apps available. Anyone who really cares about
compilation time, such as owners of older boxen, can gain more time by
selectively installing packages than they might lose by the overhead incurred.
</p>
@@ -247,62 +251,54 @@
<body>
<p>
-The most obvious improvement would be to distribute separate tarballs for the
-split ebuilds, instead of unpacking pieces of the monolithic tarballs (kdebase
-etc.) distributed by upstream. This would eliminate two of the three
-overhead factors slowing down the split ebuilds: repeated extraction of the
-large tarballs and makefile regeneration (the <c>make -f
-admin/Makefile.cvs</c> phase mentioned above).
+Most or even all of the split ebuilds' performance issues are tied to autotools
+- autoconf, automake and other tools which manage the <c>./configure;make;make
+install</c> build system used in KDE 3.x.
</p>
<p>
-This leaves us with the issue of repeatedly running configure. The proper
-solution to this is confcache: a configure cache shared between emerge runs. An
-implementation already exists in the development branch of portage (the tool,
-not the package tree); a stable release with confcache is expected in half a
-year or so.
+KDE 4 will (as far as we can tell now) adopt a completely new build system,
+which among other things will greatly reduce the time its equivalent of a
+<c>make -f admin/Makefile.common; ./configure</c> will take. Hopefully, it will
+also make it much easier to create a small tarball for each split ebuild by
+lowering the cost of generating its equivalent of configure scripts (if any).
+</p>
+
+<p>
+Previously, confcache had been considered as a way to lower the cost of
+repeatedly running autoconf-generated configure scripts. Confcache is a
+method of caching the results of configure tests. However, there is still no
+confcache implementation in the stable (2.0) portage tree. Even if one is added
+in the future, it may not come soon enough for us to work on using it in the
+KDE ebuilds; we may elect to wait for KDE 4.
</p>
</body>
</section>
+</chapter>
+
+<chapter>
+<title>Split ebuilds FAQ</title>
<section>
-<title>Other factors offsetting split ebuilds slowdown</title>
+<title>Why are some split packages missing the newest ebuild versions?</title>
<body>
<p>
-The previous section listed methods of improving the performance of the
-split ebuilds specifically. Next, we will briefly mention some future speedups
-which are equally applicable to the monolithic ebuilds. Such speedups help
-make the split ebuilds 'fast enough', apart from comparisons with less
-featureful solutions such as the monolithic ebuilds.
+As explained above, not all applications are really updated between minor KDE
+releases, and so not all applications receive new ebuild versions. For
+instance, libkdenetwork wasn't updated in 3.5.0_beta2, so the latest ebuild
+available with that release was 3.5_beta1.
</p>
-<ul>
- <li>
- KDE 4.0 should be able to use <uri
- link="http://www.kde.me.uk/index.php?page=unsermake">unsermake</uri>
- instead of automake, which speeds up compilation in some scenarios; our KDE
- 3.4 ebuilds may eventually use unsermake as well.
- </li>
- <li>
- The split ebuilds support the kdexdeltas USE flag, which allows downloading
- binary diffs between release tarballs to save on bandwidth usage.
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2005-11-30 10:28 Xavier Neys
0 siblings, 0 replies; 8+ messages in thread
From: Xavier Neys @ 2005-11-30 10:28 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 05/11/30 10:28:25
Modified: xml/htdocs/doc/en kde-split-ebuilds.xml kde-config.xml
Log:
#113964 Large update from Gregorio
Revision Changes Path
1.9 +10 -46 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.9&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.9&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml.diff?r1=1.8&r2=1.9&cvsroot=gentoo
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- kde-split-ebuilds.xml 30 Oct 2005 18:26:17 -0000 1.8
+++ kde-split-ebuilds.xml 30 Nov 2005 10:28:25 -0000 1.9
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.8 2005/10/30 18:26:17 so Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.9 2005/11/30 10:28:25 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -11,6 +11,9 @@
<author title="Author">
<mail link="danarmak@gentoo.org">Dan Armak</mail>
</author>
+<author title="Editor">
+ <mail link="greg_g@gentoo.org">Gregorio Guidi</mail>
+</author>
<abstract>
With KDE 3.4, the 'split ebuilds' were introduced into Portage. This page
@@ -22,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.6</version>
-<date>2005-10-30</date>
+<version>1.7</version>
+<date>2005-11-30</date>
<chapter>
<title>The Split KDE Ebuilds</title>
@@ -422,55 +425,16 @@
</body>
</section>
<section>
-<title>How can I unmerge an older KDE?</title>
-<body>
-
-<p>
-Suppose KDE 4.0 comes out and you want to unmerge the split ebuilds for KDE
-3.4. Because they belong to different slots, emerge won't do this for you, so
-another way is needed.
-</p>
-
-<p>
-A proper solution to this problem requires modifications to portage. One such
-solution is described in
-<uri link="http://www.gentoo.org/proj/en/glep/glep-0021.html">GLEP 21</uri>.
-Until that is implemented, however, we must resort to scripts like the one
-given below.
-</p>
-
-<p>
-Fortunately, all KDE ebuilds belong to the kde-base directory (and all ebuilds
-in the kde-base category come from kde.org). So the following code works:
-</p>
-
-<pre caption="Removing KDE 3.4 from the system">
-# <i>for x in `ls /usr/portage/kde-base`; do</i>
-> <i>if [ "$x" != "CVS" ]; then</i>
-> <i>echo -n "=kde-base/$x-3.4* "</i>
-> <i>fi</i>
-> <i>done |xargs emerge -Cp</i>
-</pre>
-
-<p>
-The above looks a bit hackish, but ultimately it's not a hack because all
-we really need is a list of ebuilds from kde-base. That's a very simple task
-and so there will always be easy ways to accomplish it.
-</p>
-
-</body>
-</section>
-<section>
<title>How can I list/unmerge all split ebuilds derived from a given package?</title>
<body>
<p>
The objective here is to list all split kde ebuilds derived from, say, the
kdebase monolithic ebuild. Once again, the proper implementation (such as <uri
-link="http://www.gentoo.org/proj/en/glep/glep-0021.html">GLEP 21</uri>)
-would make this trivial. Today, however, you must become involved in the
-KDE eclasses' implementation details to some degree. So, if you use any of
-these approaches in a script that's not for private use, tell us about it.
+link="/proj/en/glep/glep-0021.html">GLEP 21</uri>) would make this trivial.
+Today, however, you must become involved in the KDE eclasses' implementation
+details to some degree. So, if you use any of these approaches in a script
+that's not for private use, tell us about it.
</p>
<p>
1.16 +242 -70 xml/htdocs/doc/en/kde-config.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-config.xml?rev=1.16&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-config.xml?rev=1.16&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-config.xml.diff?r1=1.15&r2=1.16&cvsroot=gentoo
Index: kde-config.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-config.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- kde-config.xml 20 Oct 2005 11:48:39 -0000 1.15
+++ kde-config.xml 30 Nov 2005 10:28:25 -0000 1.16
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-config.xml,v 1.15 2005/10/20 11:48:39 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-config.xml,v 1.16 2005/11/30 10:28:25 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -11,6 +11,9 @@
<author title="Author">
<mail link="swift@gentoo.org">Sven Vermeulen</mail>
</author>
+<author title="Editor">
+ <mail link="greg_g@gentoo.org">Gregorio Guidi</mail>
+</author>
<abstract>
One of the most used desktop environments is KDE. This guide tries to describe
@@ -21,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.10</version>
-<date>2005-10-20</date>
+<version>1.11</version>
+<date>2005-11-30</date>
<chapter>
<title>What is the K Desktop Environment?</title>
@@ -94,8 +97,9 @@
</p>
<p>
-KDE is also able to automatically mount devices for you. To use this feature,
-add <c>hal</c> to your USE variable.
+You should also add <c>hal</c> to your USE variable now if you want to add support
+for mounting devices automatically as explained below in
+<uri link="#kde_device_mounting">Setup KDE to Mount Devices</uri>.
</p>
<p>
@@ -107,13 +111,19 @@
</body>
</section>
<section>
-<title>Installing KDE < 3.4</title>
-<body> <!-- TODO Remove this section when 3.4 is stabilized on all archs -->
+<title>Installing KDE as Monolithic Packages</title>
+<body>
+
+<p>
+The KDE project releases new versions of its desktop environment as a set of
+about 16 big packages, each containing many applications (thus they are called
+"monolithic"), so you need to decide which of these packages you want to
+install.
+</p>
<p>
-Second, you need to think on what you want to install from the KDE distribution.
-As mentioned before, KDE is very feature-rich and embraces lots of packages. You
-don't have to believe our word for it -- just check yourself :)
+If you want to see what it looks like to have all these packages installed,
+just check yourself:
</p>
<pre caption="Listing all packages KDE would install">
@@ -121,10 +131,10 @@
</pre>
<p>
-If you're not interested in installing all those packages, you can emerge the
-individual packages. You will most definitely want the <c>kdebase</c> package as
-it contains KDE's base packages and necessities. The following table lists some
-of the other available packages that you can install.
+If you're not interested in installing all those packages, you can emerge them
+individually. You will most definitely want the <c>kdebase</c> package as it
+contains KDE's base packages and required dependencies. The following table
+lists some of the other available packages that you can install.
</p>
<table>
@@ -143,15 +153,15 @@
<ti>kdeadmin</ti>
<ti>
KDE Administrative tools, such as <c>KCron</c> (Task Scheduling),
- <c>KUser</c> (User Management) and <c>KDat</c> (Backup Management)
+ <c>KUser</c> (User Management) and <c>KDat</c> (Backup Management).
</ti>
</tr>
<tr>
<ti>kdeartwork</ti>
<ti>
Various art-related stuff, including screen savers and themes. See also <uri
- link="http://artist.kde.org">artist.kde.org</uri> for more KDE related
- artwork
+ link="http://www.kde-artists.org/">www.kde-artists.org</uri> for more KDE related
+ artwork.
</ti>
</tr>
<tr>
@@ -178,15 +188,6 @@
</ti>
</tr>
<tr>
- <ti>kde-i18n</ti>
- <ti>
- Internationalization-related files for KDE. This includes support for
- foreign languages (and currencies, number/date formats, ...) and
- documentation. See also the <uri link="http://i18n.kde.org">KDE i18n
- project</uri> for more information.
- </ti>
-</tr>
-<tr>
<ti>kdemultimedia</ti>
<ti>
Multimedia-related applications, including support for CD, MP3, DVD,
@@ -198,9 +199,9 @@
<tr>
<ti>kdenetwork</ti>
<ti>
- Network-related applications such as <c>kppp</c> (Dial-In) and <c>lisa</c>
- (Networking). Note that <c>konqueror</c> (File Manager <e>and</e> Browser)
- is part of <c>kdebase</c>!
+ Network-related applications such as <c>Kopete</c> (Multi-Protocol Instant
+ Messaging), <c>kppp</c> (Dial-In) and <c>KSirc</c> (IRC client). Note that
+ <c>konqueror</c> (File Manager <e>and</e> Browser) is part of <c>kdebase</c>!
</ti>
</tr>
<tr>
@@ -236,6 +237,14 @@
terminal), <c>kfloppy</c> (Floppy-related actions), etc.
</ti>
</tr>
+<tr>
+ <ti>kde-i18n</ti>
+ <ti>
+ Internationalization files for KDE. This includes translated
+ documentation. See also the <uri link="http://i18n.kde.org">KDE i18n
+ project</uri> for more information.
+ </ti>
+</tr>
</table>
<p>
@@ -248,20 +257,26 @@
</pre>
<p>
-In case you wonder: compiling KDE does take a while :)
+In case you wonder: compiling KDE does take a while.
</p>
</body>
</section>
<section>
-<title>Installing KDE >= 3.4</title> <!-- TODO rename to "Installing KDE" -->
+<title>Installing KDE as Split Packages</title>
<body>
<p>
-More recent KDE versions (from 3.4 onwards) are presented as a plethora of
-<uri link="/doc/en/kde-split-ebuilds.xml">split ebuilds</uri>, making it a tad
-more difficult to know what to install and what not. Gentoo does provide a few
-meta packages that will pull in a certain amount of KDE packages for you:
+If you want to have even more control on what parts of KDE you install, you
+have the possibility to install just the single KDE applications that you need.
+To know more about the ebuilds for the individual KDE programs see the <uri
+link="/doc/en/kde-split-ebuilds.xml">Split Ebuilds HOWTO</uri>.
+</p>
+
+<p>
+Knowing what to install and what not is a tad more difficult with split ebuilds.
+However, Gentoo does provide a few meta packages that will pull in a certain
+amount of KDE packages for you:
</p>
<ul>
@@ -292,24 +307,16 @@
<th>Description</th>
</tr>
<tr>
- <ti><c>amarok</c></ti>
+ <ti><c>akregator</c></ti>
<ti>
- With <uri link="http://amarok.kde.org/">amaroK</uri> you have a powerful
- music player for Unix/Linux.
+ The application to easily manage and browse internet RSS feeds.
</ti>
</tr>
<tr>
- <ti><c>k3b</c></ti>
+ <ti><c>juk</c></ti>
<ti>
- <uri link="http://www.k3b.org/">K3B</uri> is a complete CD/DVD burning
- utility with Audio support. Burning CDs was never this easy.
- </ti>
-</tr>
-<tr>
- <ti><c>kaffeine</c></ti>
- <ti>
- <uri link="http://kaffeine.sourceforge.net/">Kaffeine</uri> is a full
- featured multimedia-player for KDE.
+ The playlist oriented media player, with a look and feel resembling Apple's
+ iTunes.
</ti>
</tr>
<tr>
@@ -348,6 +355,12 @@
</ti>
</tr>
<tr>
+ <ti><c>knode</c></ti>
+ <ti>
+ KNode is the powerful KDE newsreader.
+ </ti>
+</tr>
+<tr>
<ti><c>konqueror</c></ti>
<ti>
With <uri link="http://konqueror.kde.org/">Konqueror</uri> you have a
@@ -413,7 +426,7 @@
</table>
<p>
-And this is just a small tip of the iceberg. If you want to know more about all
+And this is just the tip of the iceberg. If you want to know more about all
possible KDE applications, take a look inside the <uri
link="http://packages.gentoo.org/packages/?category=kde-base">kde-base
category</uri>. Their function should be available in the description.
@@ -432,21 +445,60 @@
<p>
If you are happy with the proposed result, leave the <c>-p</c> out. This
building process will take some time as KDE is a big environment. Don't be
-surprised when your system does not finish immediately :-)
+surprised when your system does not finish immediately.
</p>
+</body>
+</section>
+<section>
+<title>External KDE applications</title>
+<body>
+
<p>
-If you want KDE to auto-mount your devices you'll need to install <c>dbus</c>,
-<c>hal</c> and <c>ivman</c> as well after which you add each one of them to the
-default run level:
+The number of KDE applications is not limited to those shipped with the
+official KDE releases, but includes hundreds of other applications that use the
+KDE framework and libraries. Here we list just a few of the most popular ones.
</p>
-<pre caption="Setup auto-mounting">
-# <i>emerge dbus hal ivman</i>
-# <i>rc-update add dbus default</i>
-# <i>rc-update add hald default</i>
-# <i>rc-update add ivman default</i>
-</pre>
+<table>
+<tr>
+ <th>Ebuild name</th>
+ <th>Description</th>
+</tr>
+<tr>
+ <ti><c>koffice</c></ti>
+ <ti>
+ <uri link="http://www.koffice.org/">KOffice</uri> is the comprehensive KDE
+ office suite, featuring applications for word processing (KWord),
+ spreadsheet calculations (KSpread), presentation (KPresenter), image
+ manipulation (Krita), database management (Kexi) and much more.
+ Just as KDE can be installed through the <c>kde</c> or <c>kde-meta</c>
+ ebuilds, you can install KOffice as a single package (<c>koffice</c>) or as
+ a set of individual packages (<c>koffice-meta</c>).
+ </ti>
+</tr>
+<tr>
+ <ti><c>amarok</c></ti>
+ <ti>
+ With <uri link="http://amarok.kde.org/">amaroK</uri> you have a powerful
+ music player for Unix/Linux.
+ </ti>
+</tr>
+<tr>
+ <ti><c>k3b</c></ti>
+ <ti>
+ <uri link="http://www.k3b.org/">K3B</uri> is a complete CD/DVD burning
+ utility with Audio support. Burning CDs was never this easy.
+ </ti>
+</tr>
+<tr>
+ <ti><c>kaffeine</c></ti>
+ <ti>
+ <uri link="http://kaffeine.sourceforge.net/">Kaffeine</uri> is a full
+ featured multimedia-player for KDE.
+ </ti>
+</tr>
+</table>
</body>
</section>
@@ -516,7 +568,7 @@
Next, KPersonalizer asks for the amount of eye-candy it should activate. The
more eye-candy you want, the funkier your KDE will be, but the more your CPU
will be stressed. However, this should be taken with a bit of salt - on a 600
-Mhz CPU with 128 Mb of memory, enabling full eye candy still results in a
+Mhz CPU with 128 Mb of memory, enabling full eye-candy still results in a
responsive system.
</p>
@@ -596,7 +648,7 @@
</pre>
<p>
-Finish up by adding <c>xdm</c> to the default run level:
+Finish up by adding <c>xdm</c> to the default runlevel:
</p>
<pre caption="Adding xdm to the default runlevel">
@@ -616,8 +668,137 @@
</body>
</section>
+<section id="kde_device_mounting">
+<title>Setup KDE to Mount Devices</title>
+<body>
+
+<p>
+KDE gives you the power to mount devices such as CDROMs or USB sticks through a
+single click in a graphical interface. To accomplish this goal you need to
+have KDE compiled with <c>hal</c> in your USE variable and to have
+<c>dbus</c>, <c>hal</c> and <c>pmount</c> installed on your system. You should
+also add <c>dbus</c> and <c>hal</c> to the default runlevel and add yourself to
+the <c>plugdev</c> group.
+</p>
+
+<pre caption="Setup device mounting">
+# <i>emerge --noreplace dbus hal pmount</i>
+# <i>rc-update add dbus default</i>
+# <i>rc-update add hald default</i>
+<comment>Add <user> to the plugdev group</comment>
+# <i>gpasswd -a <user> plugdev</i>
+</pre>
+
+<p>
+You can also have your devices automatically mounted without interaction, you
+just need to install <c>ivman</c> and add it to the default runlevel.
+</p>
+
+<pre caption="Setup auto-mounting">
+# <i>emerge --noreplace ivman</i>
+# <i>rc-update add ivman default</i>
+</pre>
+
+</body>
+</section>
</chapter>
+<chapter>
+<title>Managing KDE Installations</title>
+<section>
+<title>Multiple Installations</title>
+<body>
+
+<p>
+One peculiarity of the way KDE is managed in Gentoo is that when a new series
+of KDE appears (such as the 3.5.x series, which supersedes the 3.4.x series)
+it will be installed alongside the old one and will not overwrite it. So if
+for instance you had KDE 3.4 already installed and you emerge KDE 3.5,
+you will have two versions, one installed in <path>/usr/kde/3.4/</path> and
+the other in <path>/usr/kde/3.5/</path>.
+</p>
+<p>
+It should be noted that your settings for different KDE installations will be
+kept separate in the home directory. KDE 3.4 reads its settings from the
+directory <path>/home/<user>/.kde3.4</path>, and the first time you run
+KDE 3.5 a directory named <path>/home/<user>/.kde3.5</path> will be
+created by migrating the settings in the 3.4 directory and will be then used to
+store preferences and data.
+</p>
+
+<p>
+Another important remark to keep in mind when upgrading your KDE installation
+is that you could have problems with the external KDE applications you have
+installed (such as <c>koffice</c>, <c>amarok</c> or <c>k3b</c>) until you
+recompile them against the new KDE version. So as soon as you start using the
+new KDE you should reemerge them to make them link against the new libraries.
+</p>
+
+</body>
+</section>
+<section>
+<title>Unmerging Old Versions</title>
+<body>
+
+<p>
+Having multiple versions of KDE installed poses the problem of how to remove
+the old ones when we decide that they are not needed anymore. Unfortunately
+portage does not support unmerging a package with all its dependencies with a
+single command, so if for instance you run <c>emerge --unmerge kde</c> you will
+not remove the actual kde packages.
+</p>
+
+<p>
+To remove a KDE installation (e.g. KDE 3.4), the single packages have to be
+removed.
+</p>
+
+<pre caption="Removing KDE 3.4 packages">
+# <i>emerge --unmerge =arts-3.4* =kdelibs-3.4* =kdebase-3.4* ...</i>
+</pre>
+
+<p>
+Obviously this is very frustrating if you have many KDE packages installed.
+However this operation can be automated in many ways. The following one is
+an example.
+</p>
+
+<p>
+First we list all the packages that we want to remove.
+</p>
+
+<pre caption="Listing packages to remove">
+<comment>(List all the installed KDE packages)</comment>
+# <i>equery list kde-base/</i>
+<comment>(List all the installed KDE packages and select the ones from KDE 3.4)</comment>
+# <i>equery list kde-base/ | grep 3.4</i>
+</pre>
+
+<p>
+At this point you should double-check that the list corresponds to the packages
+that should be removed from the system. If you think it is ok, you can go on
+and pass the list to the <c>emerge --unmerge</c> command.
+</p>
+
+<pre caption="Removing selected packages">
+# <i>equery list kde-base/ | grep 3.4 | xargs emerge --unmerge --pretend</i>
+</pre>
+
+<p>
+Check again the output and reissue the command without <c>--pretend</c> to
+start the unmerging process.
+</p>
+
+<p>
+After the job has completed, the directory <path>/usr/kde/3.4/</path> should
+contain only a few files (mainly configuration files, portage has a policy to
+never touch configurations). If you desire, you can safely wipe out
+<path>/usr/kde/3.4/</path> with its content to remove what remains of KDE 3.4.
+</p>
+
+</body>
+</section>
+</chapter>
<chapter>
<title>Frequently Asked Questions</title>
<section>
@@ -651,15 +832,6 @@
<comment>(...)</comment>
</pre>
-<p>
-If you don't have an IPv6-enabled network, disable KDE's IPv6 checking by
-adding the following line to <path>/etc/env.d/99kde-env</path>:
-</p>
-
-<pre caption="Changing /etc/env.d/99kde-env">
-KDE_NO_IPV6 = 1
-</pre>
-
</body>
</section>
</chapter>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2006-01-02 10:05 Xavier Neys
0 siblings, 0 replies; 8+ messages in thread
From: Xavier Neys @ 2006-01-02 10:05 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 06/01/02 10:05:12
Modified: xml/htdocs/doc/en kde-split-ebuilds.xml
Log:
Fixed "typo"
Revision Changes Path
1.10 +2 -2 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.10&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/kde-split-ebuilds.xml.diff?r1=1.9&r2=1.10&cvsroot=gentoo
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- kde-split-ebuilds.xml 30 Nov 2005 10:28:25 -0000 1.9
+++ kde-split-ebuilds.xml 2 Jan 2006 10:05:11 -0000 1.10
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.9 2005/11/30 10:28:25 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.10 2006/01/02 10:05:11 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -243,7 +243,7 @@
Finally, installing all of KDE makes sense if you want to explore the available
packages or are setting up a multi-user environment; however, most people use
only some of the 300+ KDE apps available. Anyone who really cares about
-compilation time, such as owners of older boxen, can gain more time by
+compilation time, such as owners of older boxes, can gain more time by
selectively installing packages than they might lose by the overhead incurred.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2006-09-28 11:40 Josh Saddler
0 siblings, 0 replies; 8+ messages in thread
From: Josh Saddler @ 2006-09-28 11:40 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/09/28 11:40:41
Modified: kde-split-ebuilds.xml
Log:
Updated kde split ebuilds guide, kickstarted (see, a k-pun) by deathwing00. see bug 149149
Revision Changes Path
1.11 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?r1=1.10&r2=1.11
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- kde-split-ebuilds.xml 2 Jan 2006 10:05:11 -0000 1.10
+++ kde-split-ebuilds.xml 28 Sep 2006 11:40:41 -0000 1.11
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.10 2006/01/02 10:05:11 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.11 2006/09/28 11:40:41 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.7</version>
-<date>2005-11-30</date>
+<version>1.8</version>
+<date>2006-09-28</date>
<chapter>
<title>The Split KDE Ebuilds</title>
@@ -36,27 +36,27 @@
<p>
Until January 2005, the only KDE ebuilds in Portage were 'monolithic' ones.
-That is to say, there were only 15 ebuilds (kdebase, kdenetwork, ...), and
-each one installed many applications that did not, in fact, depend on one
-another. This was clearly a suboptimal situation, and not very Gentoo-ish,
+That is to say, there were only 15 ebuilds (<c>kdebase</c>, <c>kdenetwork</c>,
+...), and each one installed many applications that did not, in fact, depend on
+one another. This was clearly a suboptimal situation, and not very Gentoo-ish,
but it was tolerated for a long time.
</p>
<p>
-The new 'split' ebuilds (for konqueror, kmail, ...) rectified the situation by
-providing separate ebuilds for all the separate KDE applications. This gave us
-a grand total of about 330 new ebuilds in the kde-base category.
+The new 'split' ebuilds (for <c>konqueror</c>, <c>kmail</c>, ...) rectified the
+situation by providing separate ebuilds for all the separate KDE applications.
+This gave us a grand total of about 330 new ebuilds in the kde-base category.
</p>
<p>
-We still provide monolithic ebuilds for KDE 3.4 and 3.5 and they are cleanly
-interoperable with the split ones. However, the split ebuilds are the new
-default, and there will be no monolithic ebuilds for KDE 4.0.
+We still provide monolithic ebuilds for 3.5 and they are cleanly interoperable
+with the split ones. However, the split ebuilds are the new default, and there
+will be no monolithic ebuilds for KDE 4.0.
</p>
<p>
Finally, it should be mentioned that there are split ebuilds for Koffice as
-well. These provide kword, kugar etc. as separate packages.
+well. These provide <c>kword</c>, <c>kugar</c>, etc. as separate packages.
</p>
</body>
@@ -66,9 +66,9 @@
<body>
<p>
-The latest stable KDE release, as of this writing, is 3.4.3. The latest
-unstable (package.masked) is 3.5.0_beta2. Split and monolithic ebuilds for both
-releases are present in Portage.
+The latest stable KDE release, as of this writing, is 3.5.2. The latest
+unstable (~arch) is 3.5.4. Split and monolithic ebuilds for both releases are
+present in Portage.
</p>
<ul>
@@ -83,8 +83,8 @@
<li>
Finally, for the exact equivalent of one of the monolithic packages - for
instance, to get all the applications included in <c>kdebase</c> using
- split ebuilds - you can <c>emerge kdebase-meta</c> (or kdepim-meta, etc.)
- To get absolutely all KDE split ebuilds, <c>emerge kde-meta</c>.
+ split ebuilds - you can <c>emerge kdebase-meta</c> (or <c>kdepim-meta</c>,
+ etc.) To get absolutely all KDE split ebuilds, <c>emerge kde-meta</c>.
</li>
</ul>
@@ -96,20 +96,21 @@
<p>
If you have KDE 3.3.x installed, you can simply <c>emerge kde-meta</c> to
-install the 3.4.x split ebuilds without disturbing your existing installation.
-The same applies to 3.5.x.
+install the 3.5.x split ebuilds without disturbing your existing installation.
</p>
<p>
-If you have the KDE 3.4.x monolithic ebuilds installed, you must unmerge them
-before emerging the split ebuilds. However, this process can be done for each
-monolithic ebuild in turn; you don't have to unmerge all of KDE at once.
+If you have the KDE 3.4.x or 3.5.x monolithic ebuilds installed, you must
+unmerge them before emerging the split ebuilds. However, this process can be
+done for each monolithic ebuild in turn; you don't have to unmerge all of KDE
+at once.
</p>
<p>
-If you're in doubt, remember there are blocking deps in place between each
-monolithic ebuild and the split ebuilds derived from it. Portage won't allow an
-illegal state to be created, so any emerge or unmerge it allows is OK.
+If you're in doubt, remember there are blocking dependencies in place between
+each monolithic ebuild and the split ebuilds derived from it. Portage won't
+allow an illegal state to be created, so any emerge or unmerge it allows is
+OK.
</p>
</body>
@@ -138,7 +139,8 @@
</li>
<li>
Users of other desktops and leaner WMs can emerge a few KDE apps they like
- without the (quite big) overhead of the rest of, say, kdebase or kdepim.
+ without the (quite big) overhead of the rest of, say, <c>kdebase</c> or
+ <c>kdepim</c>.
</li>
<li>
Users can fine-tune the packages they have installed. Reasons you might
@@ -146,9 +148,10 @@
<ul>
<li>
- You care about compilation time. <c>emerge kdebase kdepim kdenetwork</c>
- takes far too long when what you really need is konqueror, kmail
- and kopete. Besides, CPU time is money... somewhere.
+ You care about compilation time. <c>emerge kdebase kdepim
+ kdenetwork</c> takes far too long when what you really need is
+ <c>konqueror</c>, <c>kmail</c> and <c>kopete</c>. Besides, CPU time is
+ money... somewhere.
</li>
<li>
You care about disk usage. Every unused package is that many megabytes
@@ -182,8 +185,8 @@
<p>
Split and monolithic ebuilds can be mixed freely. The only restriction is that
a monolithic ebuild can't be installed at the same time as a split ebuild
-deriving from it. There are blocking deps in the ebuilds that enforce this, so
-you can do anything emerge allows you to do.
+deriving from it. There are blocking dependencies in the ebuilds that enforce
+this, so you can do anything emerge allows you to do.
</p>
<p>
@@ -195,9 +198,9 @@
<p>
The split ebuilds are also the default ebuilds. This means that when some other
ebuild depends on a KDE application, it will want to install a split ebuild.
-However, the matching monolithic ebuild will also satisfy that dep, so you can
-emerge the monolithic ebuild manually and then emerge the ebuild that depended
-on it.
+However, the matching monolithic ebuild will also satisfy that dependency, so
+you can emerge the monolithic ebuild manually and then emerge the ebuild that
+depended on it.
</p>
</body>
@@ -268,12 +271,12 @@
</p>
<p>
-Previously, confcache had been considered as a way to lower the cost of
-repeatedly running autoconf-generated configure scripts. Confcache is a
+Previously, <c>confcache</c> had been considered as a way to lower the cost of
+repeatedly running autoconf-generated configure scripts. <c>Confcache</c> is a
method of caching the results of configure tests. However, there is still no
-confcache implementation in the stable (2.0) portage tree. Even if one is added
-in the future, it may not come soon enough for us to work on using it in the
-KDE ebuilds; we may elect to wait for KDE 4.
+<c>confcache</c> implementation in the stable (2.1) Portage tree. Even if one
+is added in the future, it may not come soon enough for us to work on using it
+in the KDE ebuilds; we may elect to wait for KDE 4.
</p>
</body>
@@ -311,7 +314,7 @@
allows selectively disabling subdirectories from compilation. Some people used
to use it to compile subsets of the monolithic KDE ebuilds. For instance,
running <c>DO_NOT_COMPILE=konqueror emerge kdebase</c> would install a kdebase
-without the konqueror application.
+without the <c>konqueror</c> application.
</p>
<p>
@@ -327,7 +330,7 @@
<ul>
<li>
- It completely breaks portage's dependency tracking. Portage does not know
+ It completely breaks Portage's dependency tracking. Portage does not know
about DO_NOT_COMPILE, and thinks the entire monolithic package has been
installed and can satisfy other packages' deps. This can cause other
packages not to emerge or not to run.
@@ -346,7 +349,7 @@
sufficient knowledge on the user's part. The only thing you can do with it
is disable a few applications from compiling. It is practically impossible
to use it to install only a few selected applications from modules like
- kdebase or kdepim.
+ <c>kdebase</c> or <c>kdepim</c>.
</li>
<li>
If I installed kmail yesterday and want to add korn today, using
@@ -377,7 +380,7 @@
For completeness' sake, I should mention that maintainers from other archs
have in fact complained about the increased workload of testing and keywording
so many separate ebuilds. We're working to resolve this and it's a major reason
-why monolithic ebuilds are in fact still available for KDE 3.4.
+why monolithic ebuilds are in fact still available for KDE 3.5.
</p>
</body>
@@ -430,7 +433,7 @@
<p>
The objective here is to list all split kde ebuilds derived from, say, the
-kdebase monolithic ebuild. Once again, the proper implementation (such as <uri
+<c>kdebase</c> monolithic ebuild. Once again, the proper implementation (such as <uri
link="/proj/en/glep/glep-0021.html">GLEP 21</uri>) would make this trivial.
Today, however, you must become involved in the KDE eclasses' implementation
details to some degree. So, if you use any of these approaches in a script
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2006-12-23 4:06 Josh Saddler
0 siblings, 0 replies; 8+ messages in thread
From: Josh Saddler @ 2006-12-23 4:06 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/12/23 04:06:36
Modified: kde-split-ebuilds.xml
Log:
removed confcache reference, and reworked kde-functions code block, bug 158864
Revision Changes Path
1.12 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?r1=1.11&r2=1.12
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- kde-split-ebuilds.xml 28 Sep 2006 11:40:41 -0000 1.11
+++ kde-split-ebuilds.xml 23 Dec 2006 04:06:36 -0000 1.12
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.11 2006/09/28 11:40:41 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.12 2006/12/23 04:06:36 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.8</version>
-<date>2006-09-28</date>
+<version>1.9</version>
+<date>2006-12-22</date>
<chapter>
<title>The Split KDE Ebuilds</title>
@@ -270,15 +270,6 @@
lowering the cost of generating its equivalent of configure scripts (if any).
</p>
-<p>
-Previously, <c>confcache</c> had been considered as a way to lower the cost of
-repeatedly running autoconf-generated configure scripts. <c>Confcache</c> is a
-method of caching the results of configure tests. However, there is still no
-<c>confcache</c> implementation in the stable (2.1) Portage tree. Even if one
-is added in the future, it may not come soon enough for us to work on using it
-in the KDE ebuilds; we may elect to wait for KDE 4.
-</p>
-
</body>
</section>
</chapter>
@@ -448,14 +439,14 @@
</p>
<pre caption="Example usage of the kde-functions functions">
-$ <i>function die() { echo $@; } # called to report errors</i>
+$ <i>function die() { echo $@; }</i> <comment># called to report errors</comment>
$ <i>source /usr/portage/eclass/kde-functions.eclass</i>
-$ <i>get-parent-package konqueror # won't work, you must specify full name</i>
-<i>Package konqueror not found in KDE_DERIVATION_MAP, please report bug # error printed</i>
-$ <i>get-parent-package kde-base/konqueror # fully qualified package name</i>
-<i>kde-base/kdebase # result printed</i>
+$ <i>get-parent-package konqueror</i> <comment># won't work, you must specify full name</comment>
+Package konqueror not found in KDE_DERIVATION_MAP, please report bug <comment># error printed</comment>
+$ <i>get-parent-package kde-base/konqueror</i> <comment># fully qualified package name</comment>
+kde-base/kdebase <comment># result printed</comment>
$ <i>get-child-packages kde-base/kdebase</i>
-<i> # (long list of packages printed here)</i>
+<comment>(Long list of packages printed here)</comment>
</pre>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2008-01-16 18:49 Jan Kundrat
0 siblings, 0 replies; 8+ messages in thread
From: Jan Kundrat @ 2008-01-16 18:49 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 08/01/16 18:49:32
Modified: kde-split-ebuilds.xml
Log:
Update wrt KDE 4.0.0 and current state of the tree
Revision Changes Path
1.14 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?r1=1.13&r2=1.14
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- kde-split-ebuilds.xml 24 Jun 2007 00:39:37 -0000 1.13
+++ kde-split-ebuilds.xml 16 Jan 2008 18:49:32 -0000 1.14
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.13 2007/06/24 00:39:37 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.14 2008/01/16 18:49:32 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.10</version>
-<date>2007-06-23</date>
+<version>1.11</version>
+<date>2007-01-16</date>
<chapter>
<title>The Split KDE Ebuilds</title>
@@ -51,7 +51,7 @@
<p>
We still provide monolithic ebuilds for 3.5 and they are cleanly interoperable
with the split ones. However, the split ebuilds are the new default, and there
-will be no monolithic ebuilds for KDE 4.0.
+will be no monolithic ebuilds after KDE 4.0.
</p>
<p>
@@ -66,9 +66,10 @@
<body>
<p>
-The latest stable KDE release, as of this writing, is 3.5.5. The latest
-unstable (~arch) is 3.5.7. Split and monolithic ebuilds for both releases are
-present in Portage.
+The latest stable KDE release, as of this writing, is 3.5.7. The latest
+unstable (~arch) is 3.5.8. Split and monolithic ebuilds for both releases are
+present in Portage. The 4.0.0 release is about to enter the tree in hardmasked
+state.
</p>
<ul>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml
@ 2008-01-17 0:14 Jan Kundrat
0 siblings, 0 replies; 8+ messages in thread
From: Jan Kundrat @ 2008-01-17 0:14 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 08/01/17 00:14:40
Modified: kde-split-ebuilds.xml
Log:
As scen kindly pointed out, we have 2008, not 2007 :)
Revision Changes Path
1.15 xml/htdocs/doc/en/kde-split-ebuilds.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml?r1=1.14&r2=1.15
Index: kde-split-ebuilds.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- kde-split-ebuilds.xml 16 Jan 2008 18:49:32 -0000 1.14
+++ kde-split-ebuilds.xml 17 Jan 2008 00:14:40 -0000 1.15
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.14 2008/01/16 18:49:32 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/kde-split-ebuilds.xml,v 1.15 2008/01/17 00:14:40 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -26,7 +26,7 @@
<license/>
<version>1.11</version>
-<date>2007-01-16</date>
+<date>2008-01-16</date>
<chapter>
<title>The Split KDE Ebuilds</title>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2008-01-17 0:14 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-28 11:40 [gentoo-doc-cvs] cvs commit: kde-split-ebuilds.xml Josh Saddler
-- strict thread matches above, loose matches on Subject: below --
2008-01-17 0:14 Jan Kundrat
2008-01-16 18:49 Jan Kundrat
2006-12-23 4:06 Josh Saddler
2006-01-02 10:05 Xavier Neys
2005-11-30 10:28 Xavier Neys
2005-10-30 18:26 Stefano Rossi
2005-09-09 7:26 Shyam Mani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox