From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: KDE-4.2 and KDE-3.5
Date: Sun, 01 Feb 2009 01:00:14 +0200 [thread overview]
Message-ID: <gm2l5h$n7c$1@ger.gmane.org> (raw)
In-Reply-To: <20090131222758.GA4567@ca.inter.net>
Philip Webb wrote:
> 090131 Nikos Chantziaras wrote:
>> Dmitry Makovey wrote:
>>> I was tracking KDE-4.x for a while while sticking to "stable" KDE-3.5.,,
>>> Trying to get KDE-4.2 installed spits out a blocker:
>>> [blocks B ] <=kde-base/kdebase-startkde-3.5.10
>>> ("<=kde-base/kdebase-startkde-3.5.10" is blocking kde-base/kdelibs-4.2.0)
>>> which for me means switching to *2* testing platforms (3.5.10 and 4.2)
>>> Now my question is: how safe is it to do a workaround
>> KDE 3.5.10 is *not* masked. It's in ~arch.
>> It should be a safe/stable update since it's a bug-fix release
>
> I've been using 3.5.10 since 080924 without any problems:
> just update to that & then try emerging 4.2.0 .
>
> My feeling remains that KDE 4 is more eye-candy than useful,
That has always been a goal with KDE anyway. We can't have OS X and
Vista/Windows 7 win those beauty contests, now can we ;)
Anyway, 4.2.0 is what sealed the deal for me. I went back to KDE 3
after trying KDE 4.0. I went again back to 3 after trying the first 4.1
version. And again after the latest 4.1 update (4.1.4). With 4.2.0, it
seems it is a worthy replacement for KDE 3 for me. I didn't login to
KDE 3 since I installed it (2 days ago). I like it, but I hope no
show-stopper shows up :P
next prev parent reply other threads:[~2009-01-31 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <122318397.1415181233432347614.JavaMail.root@avocado.cs.athabascau.ca>
2009-01-31 20:09 ` [gentoo-user] KDE-4.2 and KDE-3.5 Dmitry Makovey
2009-01-31 21:35 ` [gentoo-user] " Nikos Chantziaras
2009-01-31 22:27 ` Philip Webb
2009-01-31 23:00 ` Nikos Chantziaras [this message]
2009-01-31 22:33 ` Dale
2009-02-01 10:22 ` [gentoo-user] " Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gm2l5h$n7c$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox