Gentoo KDE Guide

@@ -41,123 +44,56 @@ =20

KDE 3 is no longer maintained by upstream, with 3.5.10 being their last = release. -Also, most KDE 3 applications aren't maintained any more, as they alread= y have been -or are currently being ported to KDE 4. The Gentoo KDE Team, provides bo= th KDE 3 -and KDE 4 ebuilds for the base KDE and for various applications, and sup= ports a side -by side full desktop installation of KDE 3 and 4, including misc KDE app= lications. -Our advice is for you to install and use by default a full KDE 4 desktop= , and use -only the KDE 3 applications that you feel have yet to be propperly porte= d to KDE 4 -(due to missing features, random crashes etc). +Also, most KDE 3 applications aren't maintained any more, as they alread= y have +been or are currently being ported to KDE 4. The Gentoo KDE Team, provid= es both +KDE 3 and KDE 4 ebuilds for the base KDE and for various applications, a= nd +supports a side by side full desktop installation of KDE 3 and 4, includ= ing misc +KDE applications. Our advice is for you to install and use by default a= full +KDE 4 desktop, and use only the KDE 3 applications that you feel have ye= t to be +propperly ported to KDE 4 (due to missing features, random crashes etc).

=20 -Keep in mind that since KDE 3 isn't maintained by upstream any more, it = is possible -and likely that bug reports concerning KDE 3 applications may not be fix= ed, but -rather closed as WONTFIX / CANTFIX / UPSTREAM, or instead kept open for = a long time -until a fix (patch) is provided. +Keep in mind that since KDE 3 isn't maintained by upstream any more, it = is +possible and likely that bug reports concerning KDE 3 applications may n= ot be +fixed, but rather closed as WONTFIX / CANTFIX / UPSTREAM, or instead kep= t open +for a long time until a fix (patch) is provided. =20

-KDE 3 Stabilization +KDE 3 Removal =20

-Currently 3.5.9 is marked stable on all architectures (with stable keywo= rds), while -3.5.10 is in the process of stabilization (see -bug 271889) - it is already stable on the amd64 and x86 arches. -KDE 3.5.10 uses only split ebuilds, meaning that users of monolithic ebu= ilds (like -kdebase, kdepim, kdegames etc) must unemerge them manually and then proc= eed with -the installation of KDE 3.5.10 as described below. KOffice 1.6.3 is also= in the progress -of stabilization, and the last version includes only split ebuilds. So, = users of monolithic -KOffice should also unemerge it manually and emerge koffice-meta-1.6.= 3_p20090204. +Currently KDE 3.5.10 is masked for all architectures, as it is being rem= oved +from Portage.

=20

-The team is also cleaning up the various KDE 3 applications, either by r= emoving them -from the tree, if they are too old, broken and unmaintained, or by stabi= lizing the -latest version after moving the SLOT to :3.5. (bug 270945), and dropping = arts support -(with major help from Media/Video teams). When this task is finished, we= are going to -drop arts from base KDE 3 as well. +The KDE team has been cleaning up the various KDE 3 applications by remo= ving +them from the tree, as they are too old, broken and unmaintained, and by +dropping arts support (with major help from Media/Video teams). When thi= s task +is finished, we are going to drop arts from base KDE 3 as well.

=20 - -

-KDE 3.5.10 Installation - -

-The installation of KDE 3 can be done either by using the meta packages = (kdebase-meta, -kdepim-meta, kde-meta) or by using the sets. As stated before, users of = monolithic 3.5.9 -ebuilds that want to update to 3.5.10 and get strange blocks, should man= ually unemerge -monolithic 3.5.9 ebuilds (kdebase, kdepim, kdegames etc) and emerge 3.5.= 10 as explained -below. For installation using meta packages: +While using KDE 3 is not recommended due to security and bug concerns, i= f you +must install it, you can find it in the kde-sunset +overlay.

=20 -

-# emerge -av kde-meta:3.5 (contains all of KDE modules)<=
/comment>
-# emerge -av kdebase-meta:3.5 kdegames-meta:3.5 (install=
ation of chosen modules only)
-

- -Installation of KDE 3 can be done in parallel with KDE 4, because both u= se different eclasses, -thus different slotting and prefix, so they don't affect each other. = kdeprefix USE Flag -for KDE 4 (explained later) has nothing to do with KDE 3/4 mixed install= ations. +This overlay is completely unsupported by Gentoo. It's not maintained by= the KDE +team, so do not report any issues to Gentoo developers, bugzilla,= etc. =20 -

-For installation using sets check the Using Sets section. -

- -

-In case KDE 3.5.10 isn't marked stable in your architecture yet (or you = are using ~mips or -~x86-fbsd, that don't provide stable keywords any more), we provide a pa= ckage.keywords file -in kde-testing overlay under -Documentation/package.keywords directory. -

- -

-# cd /etc/portage/
-# cat /path/to/kde-3.5.keywords/file >> package.keywords
-

- -

-# cd /etc/portage/package.keywords
-# cp /path/to/kde-3.5-keywords/file .
-

- - -

-Installation of KDE 3 Applications - - -

-As stated before, KDE 3 Applications are slotted as :3.5, which allows u= sers to have them -installed along with the KDE 4 equivalents, just like in the base applic= ations. For better -administration of your system, you could take full advantage of slots an= d use slotted -package selections in your package.keywords and world file. For example: -

- -

-# echo "app-cat/application:3.5" >> /etc/portage/package.keywor=
ds[/<file>]
-(in case the KDE 3 application is still keyworded as testing)
-# emerge -av application:3.5
-

- -

-The same rules apply for KDE 4 applications, which are slotted as :4. Th= is way, the emerge -and removal of an application can be easily done without conflicts, bloc= ks, or unwanted -removals. -

+ KDE 4

@@ -165,28 +101,29 @@ =20

-KDE 4 is the current KDE version supported by upstream. The current KDE = 4 version -available through portage is 4.2.4 (this version is considered stable by= upstream). -In addition, KDE upstream provides weekly -snapshots, and a live SVN tree= . -The Gentoo KDE team provides the snapshots, trunk and latest branch live= ebuilds, -through the kde-testing overlay. To enable this, the user can hav= e multiple -parallel KDE 4 installations, with the use of the kdeprefix USE f= lag. +KDE 4 is the current KDE version supported by upstream. The current KDE = 4 +version available through Portage is 4.3.1 (this version is considered s= table by +upstream). In addition, KDE upstream provides weekly snapshots, and a live SVN tree. The Gentoo KDE team = provides +the snapshots, trunk and latest branch live ebuilds, through the +kde-testing overlay. To enable this, the user can have multiple p= arallel +KDE 4 installations, with the use of the kdeprefix USE flag.

=20

Choose what KDE version is most appropriate for you:

- - KDE from Portage (currently 4.2.4 and 4.= 3.0) - - - KDE snapshots (currently 4.3.X) - - - KDE live ebuilds - + + KDE from Portage (currently 4.3.1) + + + KDE snapshots (currently 4.3.X) + + + KDE live ebuilds +

=20 @@ -196,58 +133,59 @@ =20 -The kdeprefix USE flag is currently masked. It's unsupported -and shouldn't be used by users in any way. Use at your own risk. Read be= low -for the reasons that led to the masking of the USE flag. +The kdeprefix USE flag is currently masked. It's unsupported and +shouldn't be used by users in any way. Use at your own risk. Read below = for the +reasons that led to the masking of the USE flag. =20
The kdeprefix USE flag allows users to choose between an FHS comp= liant -install (-kdeprefix) or a slotted install in the KDE prefix (+= kdeprefix). +install (-kdeprefix) or a slotted install in the KDE prefix +(+kdeprefix).
=20
-If kdeprefix is disabled (default) KDE is installed into the FHS = compliant -location, i.e. /usr. That means that all of the files are p= ut under -/usr. This is the desired behaviour for most users. The dra= wback of -the FHS compliant install is that it will not be possible to have more t= han one -minor version of KDE side by side (previous behaviour), e.g. KDE 4.2 and= 4.3. +If kdeprefix is disabled (default) KDE is installed into the FHS +compliant location, i.e. /usr. That means that all of the f= iles are +put under /usr. This is the desired behaviour for most user= s. The +drawback of the FHS compliant install is that it will not be possible to= have +more than one minor version of KDE side by side (previous behavior), e.g= . KDE +4.3 and 4.4.
=20 - -This restriction does not apply to KDE 3 (which uses different prefix (<= path>/usr/kde/3.5)). -You can have KDE 3.5 with either -kdeprefix or kdeprefix K= DE 4.X in the same system. - - -Mixing a +kdeprefix and a -kdeprefix KDE installation is n= ot supported, nor -recommended. If you really want kdeprefix in your system, you'll have to= unmask -it and put it globally in /etc/make.conf +Mixing a +kdeprefix and a -kdeprefix KDE installation is n= ot +supported, nor recommended. If you really want kdeprefix in your system,= you'll +have to unmask it and put it globally in /etc/make.conf =20
-If kdeprefix is enabled then KDE is installed into /usr/kde= /${SLOT}, -which allows you to install KDE 4.2, 4.3, live etc. in /usr/kde/4.= 2, -/usr/kde/4.3, and /usr/kde/live for example. +If kdeprefix is enabled then KDE is installed into +/usr/kde/${SLOT}, which allows you to install KDE 4.3, live= etc. in +/usr/kde/4.3 and /usr/kde/live for example.
=20 -If you want to move between kdeprefix and -kdeprefix (or v= ice-versa), it is -recommended that you unmerge all KDE packages and then emerge it with th= e -modified flag. If this is not done, KDE installations can have trouble f= inding -certain libraries/plugins. Check Cleaning Up KDE<= /uri> -for more details. +If you want to move between kdeprefix and -kdeprefix (or +vice-versa), it is recommended that you unmerge all KDE packages and the= n emerge +it with the modified flag. If this is not done, KDE installations can ha= ve +trouble finding certain libraries/plugins. Check = Cleaning +Up KDE for more details. =20
-Recently kdeprefix got masked by default, as it caused many probl= ems, like -collisions between the same packages when having two or more KDE install= ations, -or strange behaviour even when only one +kdeprefix KDE installati= on was present -in the system. Great examples of packages with such problems are pykde4 = and -amarok. Since the Gentoo KDE Team decided to proceed with the stabilizat= ion of KDE 4 -(KDE 4.2.4 being the best candidate at this moment), those issues needed= to be resolved -first. As it was difficult to fix them, we decided to mask the use flag = instead. -If you really know what you are doing and you are sure that you w= ant +Recently kdeprefix got masked by default, as it caused many probl= ems, +like collisions between the same packages when having two or more KDE +installations, or strange behaviour even when only one +kdeprefix= KDE +installation was present in the system. +
+ +
+Great examples of packages with such problems are pykde4 and +amarok. Since the Gentoo KDE Team decided to proceed with the +stabilization of KDE 4, those issues needed to be resolved first. As it = was +difficult to fix them, we decided to mask the use flag instead. If y= ou +really know what you are doing and you are sure that you want kdeprefix unmasked and enabled in your system, add kdeprefix glob= ally to /etc/make.conf and unmask it by following the instructions = below.
@@ -260,111 +198,30 @@

-Installing KDE 4.2.4 or KDE 4.3.0 (from Portage) +Installing KDE 4.3.1 (from Portage) =20 - -KDE 4.3.0= is in -Portage tree but hardmasked (until bug 280312 is fixed), except for amd6= 4 -architecture. - - -
-KDE 4.2.4<= /uri> and -is the KDE 4.3.= 0 are -the KDE 4 versions that Gentoo has in Portage - they are considered by u= pstream as -the latest stable. Currently they are in the testing branch in Portage, = but in June's -meeting the Gentoo KDE Team decided to move forward with KDE 4 stabiliza= tion - 4.2.4 -being the best candidate. -
=20 -In order to minimize issues it is recommended to start with a clean envi= ronment. Read -more in Cleaning Up KDE section. +In order to minimize issues it is recommended to start with a clean envi= ronment. +Read more in Cleaning Up KDE section. =20
-Users with stable systems have to keyword the packages to proceed. -We provide a package.keywords file in kde-testing overlay under=20 -Documentation/package.keywords/ directory -for KDE 4.2 and -for KDE 4.3. -
- -
-# cd /etc/portage/ -# cat /path/to/kde-4.2.keywords/file >> package.keywords For KDE 4.2 -# cat /path/to/kde-4.3.keywords/file >> package.keywords For KDE 4.3 -
- -
-If your package.keywords is a directory instead of a file you can do the -following: +The installation can be done either by using the meta packages or by usi= ng +sets.
=20 -
-# cd /etc/portage/package.keywords -# cp /path/to/kde-4.2.keywords/file . For KDE 4.2 -# cp /path/to/kde-4.3.keywords/file . For KDE 4.3 -
- -
-KDE 4.3 is currently hardmasked for all architectures apart from amd64.S= o, -you may also need the unmask file that we provide in kde-testing = under -Documentation/package.unmask and do the following step: -
- -
-# cd /etc/portage/ -# cat /path/to/kde-4.3/unmask/file >> package.unmask -
- -
-If your package.unmask is a directory, you can do the following: -
- -
-# cd /etc/portage/package.unmask -# cp /parth/to/kde-4.3/unmask/file . -
- -
-The installation can be done either by using the meta packages or by usi= ng sets. -
- -
-For KDE 4.2 -# emerge -av kde-meta:4.2 (contains all of KDE modules)<= /comment> -# emerge -av kdebase-meta:4.2 kdegames-meta:4.2 (install= ation of chosen modules only) -For KDE 4.3 +
# emerge -av kde-meta:4.3 (contains all of KDE modules)<= /comment> # emerge -av kdebase-meta:4.3 kdegames-meta:4.3 (install= ation of chosen modules only)
=20
-For installation using sets check the Using Sets section. -
- -
-Upgrade Troubleshooting -
- -
-If you=E2=80=99re trying to upgrade from KDE 4.2, but portage gives you = nice little blocks, -there are a few things you can check: +For installation using sets check the Using Sets +section.
=20 -
-
Make sure you=E2=80=99ve synced the tree and/or kde-testing overlay= (if using it)
-
Make sure the unmask/keyword files are correct and up-to-date
-
Check that you don=E2=80=99t have any 4.2 versioned kde-base/* item= s in /var/lib/portage/world
-
Check that you don=E2=80=99t have any 4.2 versioned sets in /= var/lib/portage/world_sets
-
emerge -avDuN world =E2=80=94 you=E2=80=99ll probably get so= me messy output but all blocks should be automatically resolved
-
-

@@ -376,10 +233,11 @@ =20
-KDE upstream provides w= eekly snapshots -taken from the SVN trunk tree= . KDE now provides -4.3.X snapshot series, and after 4.4 release they are going to start wit= h 4.4.60. Beta and -Release Candidate KDE releases are following the snapshot model below: +KDE upstream provides w= eekly +snapshots taken from the SVN +trunk tree. KDE now provides 4.3.X snapshot series, and after the = 4.4 +release they are going to start with 4.4.60. Beta and Release Candidate = KDE +releases are following the snapshot model below:
=20 @@ -402,18 +260,18 @@
=20 -In order to minimize issues it is recommended to start with a clean envi= ronment. Read -more in Cleaning Up KDE section. +In order to minimize issues it is recommended to start with a clean envi= ronment. +Read more in Cleaning Up KDE section. =20 -You'll need portage-2.2_rc*, so please add ~sys-apps/portage-2.2 = entry to your -/etc/portage/package.unmask[/*] file. +You'll need portage-2.2_rc*, so please add ~sys-apps/portage-2.2 = entry to +your /etc/portage/package.unmask[/*] file. =20
-Snapshots are only available through kde-testing overlay, so you = first need to -add it: +Snapshots are only available through kde-testing overlay, so you = first +need to add it:
=20
@@ -423,14 +281,14 @@
=20
-If you're used to git repos, don't want to use layman and rather do all -the sync work yourself, you can install the repo directly: +If you're used to git repos, don't want to use layman and rather do all = the sync +work yourself, you can install the repo directly:
=20
# mkdir /<repo-base-dir> # cd /<repo-base-dir> -# git clone git://git.overlays.gentoo.org/proj/kde.git +# git clone git://git.overlays.gentoo.org/proj/kde.git
=20
@@ -475,8 +333,7 @@ through an anonymous (anonsvn) account. Gentoo, as a source based distro= , has the ability to provide live ebuilds that checkout the code either fr= om the latest branch or from trunk. Currently, we provide 4.3.9999 ebuilds = from -4.3 branch. (We recently dropped 4.2.9999 ebuilds as 4.2 branch is mostl= y -dead). +4.3 branch.
=20 @@ -495,18 +352,18 @@
=20 -In order to minimize issues it is recommended to start with a clean envi= ronment. Read -more in Cleaning Up KDE section. +In order to minimize issues it is recommended to start with a clean envi= ronment. +Read more in Cleaning Up KDE section. =20 -You'll need portage-2.2_rc*, so please add ~sys-apps/portage-2.2 = entry in your -/etc/portage/package.unmask file. +You'll need portage-2.2_rc*, so please add ~sys-apps/portage-2.2 = entry in +your /etc/portage/package.unmask file. =20
-Live ebuilds are only available through kde-testing overlay, so f= irst thing is to install -it: +Live ebuilds are only available through kde-testing overlay, so f= irst +thing is to install it:
=20
@@ -516,9 +373,9 @@
=20
-Users with stable systems have to keyword the packages to proceed. -We provide a package.keyword file in kde-testing overlay, which w= e'll -have to symlink to our package.keywords directory: +Users with stable systems have to keyword the packages to proceed. We p= rovide a +package.keyword file in kde-testing overlay, which we'll have to = symlink +to our package.keywords directory:
=20
@@ -528,7 +385,8 @@
=20
-The installation can be done either by using the meta packages or by usi= ng sets. +The installation can be done either by using the meta packages or by usi= ng +sets.
=20
@@ -550,11 +408,6 @@ See the Using Sets section for more i= nformation.
=20 - -You may be interested for Qt live ebuilds as well. Check the Qt Guide (= TODO) for -installation instructions. - -

@@ -562,38 +415,22 @@ =20
-KDE 4 Applications are slotted in :4, which allows the users to have the= m -installed along with the KDE 3 equivalents, just like in the base applic= ations. For better -administration of your system, you could take full advantage of slots an= d use slotted -package selections in your package.keywords and world file. For example: -
- -
-# echo "app-cat/application:4" >> /etc/portage/package.keywords -# emerge -av application:4 -
- -
-The same rules apply for KDE 3 applications, which are slotted in :3.5. = This way, the emerge -and removal of an application can be easily done without conflicts, bloc= ks, or unwanted -removals. -
- -
-In kde-testing you may find live ebuilds of KDE 4 applications. These ar= e slotted in :4 -as well, but they can not be installed in parallel with normal on= es. You are -free though to use live KDE 4 applications with KDE 4 from portage, or t= o use -portage KDE 4 applications with your live KDE. +In kde-testing you may find live ebuilds of KDE 4 applications. These ar= e +slotted in :4, but they can not be installed in parallel with +normal ones. You are free though to use live KDE 4 applications with KDE= 4 from +Portage, or to use Portage KDE 4 applications with your live KDE.
=20 -There is also a set with live KDE 4 applications, @kde-extras-live, in k= de-testing and -a set with Qt live applications, @qt-extras-live, in qting-edge overlay. +There is also a set with live KDE 4 applications, @kde-extras-live, in +kde-testing and a set with Qt live applications, @qt-extras-live, in qti= ng-edge +overlay. =20
+ Additional Installation/Removal Information
@@ -601,8 +438,8 @@ =20 -Portage 2.2_rcX is currently masked to allow 2.1.6 getting stable asap. = So if -you want to use sets please unmask ~sys-apps/portage-2.2. +Portage 2.2_rcX is currently masked. So if you want to use sets please u= nmask +~sys-apps/portage-2.2. =20
@@ -624,8 +461,8 @@
=20 -In case you are using kde-testing overlay you can use sets direct= ly instead -of copying them to /etc/portage/sets. +If you are using the kde-testing overlay you can use sets directly +instead of copying them to /etc/portage/sets. =20
@@ -639,7 +476,7 @@
=20
-One can install the complete KDE by running emerge -av @kde. The = specific +One can install the complete KDE by running emerge -av @kde. The = specific version equivalents are very useful to uninstall an old version, e.g. emerge -C @kde-3.5, or to reinstall all packages from a specific version, e= .g. emerge -av1 @kde-4x. Advanced features, like removing any unwante= d @@ -647,10 +484,10 @@ read more about it in Marius Mauch's (genone) blog. Part of this code has now been released in -portage-2.2_rc12 and so you can reinstall all installed packages of a se= t -with emerge -av @<set>/@installled or to have a -/etc/portage/sets/kdebase-unwanted set and then run emer= ge -av -@kdebase-@kdebase-unwanted. +portage-2.2_rc12, so you can reinstall all installed packages of a set +with emerge -av @<set>/@installed or to have a +/etc/portage/sets/kdebase-unwanted set and then run emer= ge -av +@kdebase-@kdebase-unwanted.
=20
@@ -665,7 +502,7 @@ =20 If you want to check the list of sets known to Portage run the following= : -emerge --list-sets +emerge --list-sets =20 @@ -681,13 +518,15 @@ =20
-In order to minimize issues, it is best to begin with a clean environmen= t. This is -recommended for the following cases: +In order to minimize issues, it is best to begin with a clean environmen= t. This +is recommended for the following cases:
=20

Moving from +kdeprefix to -kdeprefix (and vice versa)=
-
Downgrading KDE (eg. from snapshots/live ebuilds to portage version= )
+
+ Downgrading KDE (eg. from snapshots/live ebuilds to the Portage versi= on) +

Fully upgrading from KDE 3 to KDE 4 (and vice versa)

Moving from an old overlay

@@ -712,7 +551,8 @@
=20 -Don't forget to run depclean in order to uninstall any dependant package= s. +Don't forget to run emerge --depclean in order to uninstall any d= ependant +packages. =20 @@ -726,8 +566,7 @@
=20
-# kbuildsycoca --noincremental (for KDE 3) -# kbuildsycoca4 --noincremental (for KDE 4) +# kbuildsycoca4 --noincremental
=20 @@ -738,43 +577,34 @@ =20
With new KDE there is new translators effort in Localization instead of -Internationalization. This cause some confusion but dont worry your tran= slation -is shiped to you, just name has been changed so now for getting translat= ions use -theese comands. +Internationalization. This cause some confusion, but don't worry; just t= he name +has been changed.
=20 -
+
For KDE 4 and KOffice 2: # emerge kde-l10n # emerge koffice-l10n -For KDE 3 and KOffice 1.6.3: -# emerge kde-i18n -# emerge koffice-i18n
=20

-Configuration of ~/.kde Directory +Migrating configs from 3.5 to 4.X =20
-KDE stores its configuration files in the ~/.kde directory = by default. -In the Gentoo ebuilds this has been changed in KDE 4.1 and later to allo= w for better -integration of KDE 3.5 and 4.X when using the same user account. If you = export -$KDEHOME this behaviour will be overridden. It is strongly recommended t= hat you -do not do this. $KDEHOME will make KDE 3.5 and 4.X use the same configur= ation -directory which is usually not desired. +KDE stores its configuration files in the ~/.kde directory = by +default. In the Gentoo ebuilds this has been changed in KDE 4.X to +allow for better integration of KDE 3.5 and 4.X when using the same user +account. If you export $KDEHOME this behaviour will be overridden. It is +strongly recommended that you do not do this. $KDEHOME will make KDE 3.5= and 4.X +use the same configuration directory which is usually not desired.
=20
-KDE 3.5 uses ~/.kde and the default FHS (-kdeprefix)= KDE 4.X uses -~/.kde4. If you install KDE 4.1 using the kdeprefix USE fl= ag then the -configuration directory will default to ~/.kde4.1, for KDE = 4.2 it will -be ~/.kde4.2 and so on. -The advantage of this is that KDE 3.5 and 4.X can be run from the same u= ser -account without clobbering settings. Moving backwards in version, i.e. 4= .X to -3.5, is not supported. +KDE 3.5 uses ~/.kde and the default FHS (-kdeprefix)= KDE 4.X +uses ~/.kde4.
=20
@@ -793,6 +623,10 @@ clean configuration directory.
=20 + +Moving backwards in version, from 3.5 to 4.X, is not supported. + +
@@ -803,17 +637,15 @@ =20
-Plasmoids are new plasma tools which can enhance your desktop experience -to brand new level. Many plasmoids are available in kde-misc/ category, -on which we get our nasty hands and find it workable enought. If you fin= d out -that your favorite one is missing create bug and somebody might create i= t for -you. -If you are plasma person "want them all can't live without them" we have= set -@plasmoids which contains all plasmoids currently availible. +Plasmoids are new plasma tools which can enhance your desktop experience= . Many +plasmoids are available in the kde-misc/ category. If you find out that = your +favorite plasmoid is missing, file a bug and somebody might create it fo= r you. +If you've got to have them all, there is a set called @plasmoids which c= ontains +all plasmoids currently available.
=20 -Mostly all plasmoids are currently placed on kde-testing overlay. +Many plasmoids are in the kde-testing overlay. =20 @@ -836,8 +668,7 @@
This ebuild should be used if you want your GTK applications to use a th= eme similar to the Qt/KDE applications. Configuration can be found in -systemsetings->Appearance->GTK Styles and Fonts. For KDE-4.2 you need at= least -gtk-engines-qt-1.1-r1. +System Settings->Appearance->GTK Styles and Fonts.
=20 @@ -854,41 +685,27 @@ =20 - -
-Flash in Konqueror - - -
-If you are interested in getting flash working in konqueror point your m= ind -to guide which describes necessary st= eps for -getting it done. Latest www-plugins/adobe-flash (both 32 and 64-bit) sho= uld -work flawlessly though, maybe you'll need to Scan for Plugins under -Konqueror->Settings->Plugins. -
- - -
-
Akonadi Complains about the MySQL Config =20
-Start by checking the permissions in /usr/share/config and /usr/share/kd= e4. If you're using +kdeprefix then -check the permissions in $(kde4-config -prefix) instead of /usr/ too. If= they're 700, you need to update them -to 755 recursively. +Start by checking the permissions in /usr/share/config and +/usr/share/kde4. If they're 700, you need to update them to= 755 +recursively.
-
+ +
# chmod -R 755 /usr/share/{config,kde4}
+
If that doesn't solve the error, you need to open the akonadi configurat= ion and change the default mysql config. If you don't have the tray running, sta= rt -akonaditray, select "Akonadi Server Configuration", activate "Us= e internal -MySQL server" and then press the test button. -If you want to use the mysql server and not the embbeded executable, you= 'll need to -ensure that mysql is running. +akonaditray, select "Akonadi Server Configuration", activate "Us= e +internal MySQL server" and then press the test button. If you want to u= se the +mysql server and not the embedded executable, you'll need to ensure that= mysql +is running.
=20 @@ -898,16 +715,15 @@ =20
-Start by checking the permissions in /usr/share/config and if you're usi= ng +kdeprefix in -$(kde4-config -prefix)/share/config. If they're 700, you need to update = them to 755. -Check previous section. -If that doesn't solve the error, check the following notice in the kdm e= build: +Start by checking the permissions in /usr/share/config. If they're 700, = you need +to update them to 755. Check previous section. If that doesn't solve t= he +error, check the following notice in the kdm ebuild:
=20
If when you restart xdm, kdm fails to start with a message like "gentoo = kdm[2116]: X server startup timeout, terminating" in /var/log/messages, uncomment the= ServerTimeout -line in "grep kdmrc /var/db/pkg/kde-base/kdm-4.2.0/CONTENTS | cut -f2 -d= " "" +line in "grep kdmrc /var/db/pkg/kde-base/kdm-4.3.1/CONTENTS | cut -f2 -d= " "" and be sure to increase the timeout - 60 should work
=20 @@ -922,16 +738,16 @@
=20
-If not, enable them by replacing status with start, and use -the command rc-update add dbus default for every one -of them to add them to default runlevel. +If not, enable them by replacing status with start, and us= e the +command rc-update add dbus default for every one of them to add t= hem to +default runlevel.
=20
-Finally, KDM could fail due to errors in xorg.conf. Take a -look in logs: /var/log/Xorg.0.log and -/var/log/kdm.log and fix xorg.conf accordingly. -For additional help you can find us in IRC (#gentoo-kde at Freenode). +Finally, KDM could fail due to errors in /etc/X11/xorg.conf= . Take a +look in your logs: /var/log/Xorg.0.log and +/var/log/kdm.log and fix xorg.conf accordingly= . For +additional help you can find us in IRC (#gentoo-kde at Freenode).
=20 @@ -941,9 +757,10 @@ =20
-So that the battery applet or other solid notifications can show the rel= evant info, -you need dbus and hald running. +So that the battery applet or other solid notifications can show the rel= evant +info, you need dbus and hald running.
+
# /etc/init.d/dbus status # /etc/init.d/hald status