| 1 |
On Thu, Jun 11, 2009 at 23:07, Volker Armin |
| 2 |
Hemmann<volkerarmin@××××××××××.com> wrote: |
| 3 |
> please explain me why this option is bad? |
| 4 |
> |
| 5 |
> I can give you examples why it is good: |
| 6 |
> -you can have multiple versions of kde installed (well, you could in the past, |
| 7 |
> until someone started to put crap into python's directories). |
| 8 |
> and |
| 9 |
|
| 10 |
Its not that simple |
| 11 |
KDE wasn't designed to work like this, kdeprefix is a Gentoo Thing |
| 12 |
that is not supported by upstream. |
| 13 |
|
| 14 |
Multiple issues can arise when using kdeprefix, things not working, |
| 15 |
misc kde4 apps linking to wrong kde4 versions, etc. |
| 16 |
|
| 17 |
If you know what you're doing (and how to fix stuff when it breaks ;) |
| 18 |
kdeprefix can be useful. But its primarily meant for developers who |
| 19 |
want to test newer kde versions. Most users should stick to -kdeprefix |
| 20 |
which is widely tested and its upgrade path is cleaner and thoroughly |
| 21 |
checked before each release. |
| 22 |
|
| 23 |
> - it makes updates risk free. You go from X.Y.Z to X.Y.Z+1 or X.Y+1 - and |
| 24 |
> before you do so, you just copy the whole kde dir. In case of severe bugs (and |
| 25 |
> especially with kde 3 you always had some nasty bugs), you just copy the |
| 26 |
> directory back and can use kde in the hours portage needs to recompile stuff - |
| 27 |
> or in the minutes it needs to install from packages (well, split ebuilds |
| 28 |
> increased that time A LOT). |
| 29 |
|
| 30 |
imho its better to just keep binary packages of stuff you've installed. |
| 31 |
if your update fails and you need your system asap, you just emerge |
| 32 |
your binaries back in no time :) no cp'ing or other strange |
| 33 |
out-of-portage stuff |
| 34 |
|
| 35 |
-- |
| 36 |
Alex Alexander || wired |
| 37 |
Gentoo QT && KDE Herd Tester |
| 38 |
http://www.linuxized.com |
Archives