


This is not correct. KDE 4.0 e.g. comes without PIM applications.Let_Me_Be wrote:KDE4 contains all aplications
Actually it's the first time KDE 3 is reasonably stable, minus some known quirks and some stuff upstream doesn't maintain actively since quite a while. KDE 3 will live on for years, while KDE 4 will probably need another one or two years, before it may match the functionality and quality of the latest KDE 3 release.Let_Me_Be wrote:KDE 3.5 is going to be deprecated very soon, I don't see any posibility supporting both KDE 4 and KDE 3.5 properly.

i'm running from overlay, and let me tell you... it is far better than previous beta versions.kalos wrote:Well I just downloaded the Kubuntu disc with KDE4 on it, and I have faith that when it hits the Portage tree it will be better. I can't believe the amount of bugs just booting into the DE on the Kubuntu Live disc. I'm glad that the devs decided to actually place 4.0.0 into the tree, but I think I will wait a while before trying it out on my main machine.

... except for the way it randomly crashes when dragging4.x is much better than the 3.x
Please report these bugs! A backtrace after a crash would be very helpful.albright wrote:... except for the way it randomly crashes when dragging4.x is much better than the 3.x
the sky around ... (and - curiously - draws the crescent
moon illuminated from the wrong side!! - this does *not*
happen in the 3.5 version)
At this pace we will be getting the ebuilds the same day that KDE4 goes into debian stableGivePeaceAChance wrote:Any idea how long that'll be?
well, the overlays for it is present and should already work for installing the packages. i think that the problem is that compiling all the stuff and being sure that it doesn't break something else while also mantaing other more important things will get the ebuilds to be delayed. speaking of other distro, of what i know the things stands in this way:At this pace we will be getting the ebuilds the same day that KDE4 goes into debian stable. I'm not blaming the packagers or anything like that, but even in this world of open source and volunteers, the one that freely takes the responsibility should act accordingly. It's not only we as users, but there are also some distributions that depend on the ebuilds to satisfy their customers. I've been a Gentoo die hard for the last 6-7 years and never complained, and I'll probably stay like that for a lot of time, but on this occasion Gentoo has sadly proven that it is not the distro to trust. I'm sure that there are very good reasons for this delay, but even knowing that, it is also a fact that a KDE major is not the same as 'yet another little rev of [put your favourite obscure package here]'. I'm sure that this is not what the devs want to hear/read, but it is what I think. Sorry! There is also all that crap about 'do not ask when', 'every WHEN delays it one more day', etc... Of course I could do it by myself, but it happens that I've not assumed my responsibility as a dev while others have done. I'm sure that the ebuilds would eventually come and all of us will be enyoing and forgotting, but you like it or not, this has been the first time in 7 years that I've looked (only looked) at other 'Linux flavours'.
Anyway, keep the good work on the other areas and let it be good in KDE too.
Regards.

Only 3.97.0 and the svn are in the normal overlay at present.beso_1717 wrote:well, the overlays for it is present and should already work for installing the packages.
Is that a hunch, or more recent information I've missed?i think that the ebuilds will be ready towards the end of this week or at the beginning of the next one.

While KDE 4.0.0 is only the first release of this Major Release Circles. I think it is save to say that it is for now KDE 4. As will be all the following KDE 4.x.y Versions. So I agree with you. It should be in the unstable Part of the portage system.zAfi wrote:we should not forget that we're actually not talking about KDE4 but about KDE 4.0. KDE4 will still take a long time with some releases, some more patches and a lot more bug fixes.
Some kdedev stated some time ago (don't ask me where) that kde 3.5 was actually the way they wanted to have kde3, so i don't think gentoo should wait for including 4.0 in ~x86. Else we won't have kde4 added till 5.0 is out (or something like that^^). And for my understanding the ~x86 branch is exactly for software like that, isn't it?

KDE 4.0.0 isn't worth switching distros over.Enjolras wrote:I'm sure that the ebuilds would eventually come and all of us will be enyoing and forgotting, but you like it or not, this has been the first time in 7 years that I've looked (only looked) at other 'Linux flavours'.

Of course not, that's why I only 'looked at'StifflerStealth wrote:KDE 4.0.0 isn't worth switching distros over.Enjolras wrote:I'm sure that the ebuilds would eventually come and all of us will be enyoing and forgotting, but you like it or not, this has been the first time in 7 years that I've looked (only looked) at other 'Linux flavours'.
While all of this is true, that shouldn't be an issue for the distro. If KDE 4.0.0 is not ready for the distro users, then it is distro devs' fault. If KDE 4.0.0 is buggy and unstable, then it is mainstream devs fault'. Just for delaying the ebuilds the mainstream code won't be magically better. But as I said in my previous message, all of this will be forgotten once the ebuilds are out and we all realize that KDE 4.0.0 is not worth all this buzz. I think that the problem here is not with these very ebuilds but with the fact that this is probably the first time in Gentoo's history that an important piece of software such is a new KDE major is not ready for us even before public release.KDE 4.0.0 really is rough and in some cases unusable. You should not make it a main desktop yet. For example, in Konq file manager, you cannot copy and paste files between folders. The KDE devs know about it, but it's not fixed yet in SVN. copy and paste is the one of the whole reasons for a file manager. My point is that it is really rough, and (this is to everyone) to have this much drama over the release of a piece software is ****** nonsense. Seriously folks, use the svn of KDE4, because it is in far better shape than the tagged 4.0.0. Just look at the commit logs and you will see proof of that.
So, I ask this nicely: Stop the drama. KDE 4.0.0 is not worth all this. This is coming from a hard core user of KDE as well. I helped with the pertty patches and KDEMod on Arch for a bit, just because I love KDE and I want to see things tweaked, but KDE 4.0.0 is not worth all this hassle. Yeah, it's nice and has a new bells and whistles that are cool, but they all do not function properly yet. Give it time and then it will be worth all the hassle, but not until then.
No more drama please. No more war. No more speculation. No more stupid sayings like "We'd rather see rough ebuilds in portage than no ebuilds at all" (that will never happen, and yes, people have said stuff to this affect).
Remember: "Good things come to those who wait." An extremely wise and old person that said that a very long time ago, but it is very, very true.


From my understanding, Gnome not working is not a Gentoo issue, but a Gnome issue. If you experience a not working Gnome, go to the Gnome's website and file bugs. That is the only way Gnome will work again, not by discussing it on a Distribution's website. Go to the Gnome devs directly to get your problem solved. This is to all Gnome users.troyt wrote:I'm willing to wait for a working KDE 4.0 release - but I have to wonder about the double-standard I see with GNOME: I've been a user of Gentoo for 5 years now; it's not like using Gentoo is a foreign concept to me.
However, on all of my Gentoo systems (4-5 of them), GNOME simply doesn't work - and that's for the stable release, not ~arch.
I haven't been able to load GNOME on Gentoo for about 18 months now, in spite of many complete re-builds of everything GNOME.
Whenever I post to the forums asking why GNOME won't work, the only thing I hear is "I have that problem too... if you figure it out, let me know"
Why is it OK to mark GNOME as "stable" when myself and quite a few other users can't even get the cursed thing to load the desktop (even after removing and re-installing all of GNOME), yet when KDE is in the same state, it won't even make it into portage as hardmasked?
I have no intention of hijacking a thread; I gave up on GNOME. But why is it acceptable for GNOME to be completely broken for many users, yet be marked as "stable", while KDE 4.0 isn't even allowed into portage hardmasked?

The difference is 2.18 was a buggy minor release the Gnome 2 release circle. In the Release circle time of gnome it would be something like the KDE 3.4 and KDE 3.5 while there are improvements between those minor releases, they are so similar, that if there are problems with one version, it can corrupt the hole system.Ray ishido wrote:Hi all,
just my 2 cents to try to show how the pb is complex.
I am personaly using gnome without any pb. I remenber that when the version 2.18 was'nt in portage a week or two after it was disponible. of course a lot of people were waiting for this version and the debate were the same as here ("why it is not in portage?", "other distro already have packages",...). As I was impatient, and as other gentooers report few bug, I tried an ovelay an everything crashed. At this moment I understood the devs decision. If they had put it into portage, I bet the forum would have been full of message asking why it crashed.
I am very impatient to test kde 4.0, but reports I read from other distro's users (mainly on opensuse) are saying it's quite a buggy version, só as an overlay already exist, I think it would be a good idea to stop this debate and respect the dev's choice.