I did search, but just not too hard. Of course KDE will make it into portage eventually. I stay away from anything which requires overlay, so I suppose I'll be staying away from KDE 4 for a while unfortunately..Veldrin wrote:First of all, please use the search function, this questions has been answer at least once..
but to make it a little less painful:
KDE4.0 probably won't get into portage, but you'll have access to the ebuilds on the kde-overlay.
They moved from svn to git.heini wrote:Can anybody tell me what happened to it? The last commit was 3063, which deleted the top level directory and had a very short commit message of "Gone like the wind."Veldrin wrote:... but you'll have access to the ebuilds on the kde-overlay.
Bye...
Dirk
Code: Select all
git clone git://www2.mailstation.de/git/genkde4svn-pubTetsting is for fairly usable stuff, without (major) known and unknown issues. KDE 4 is in large parts a whole rewrite and version 4.0 is a) missing functionality you're used to from KDE 3.5 as there was no time improve or (re-)implement everything useful, but the foundations were laid for a richer application stack for the years to come and b) is dedicated to developers, early adopters, enthusiasts - but not the ordinary user. It's to fresh and not stable enough to go into testing.cogent wrote:Sorry for my naiveness, but isn't this what the testing branch is for? To have software like KDE4.0?
Right, there's a lot of hidden potential, but 4.0 won't be that impressive at all for the average user. Plus there's no point in migrating unless you need any new features.Let_Me_Be wrote:KDE4 contains all aplications, the only thing about it is that some of them are still the old ones, not using the new cool features, and believe me, most of apps won't be untill KDE 4.2 (for example Kopete or KOffice).
No. If you want to migrate just for the coolness or the sake of migrating, you can use overlays. Portage devs have already a lot of work maintaining stable software, they don't need to bite their own asses by inserting another couple of thousands of unstable new ebuilds that will require continuous attention to be able to compile. Binary distros are another matter: they just compile one time and everything is right. But a source distro is not the same, you need to understand that.If you want to keep KDE out of portage until KDE 4.2 then you will loose a huge amount of users.
No!KDE 3.5 is going to be deprecated very soon
And my I suggest that everyone reads this blog entry from Aarin Seigo - KDE head dev....No!
<snip>
Sure that the main focus is going to be kde4, no doubt about that. But that doesn't automatically render kde3.x unsupported.
Yes, it's all about choice. You have the choice to use an overlay. If you aren't experienced enough to maintain an overlay you will not be experienced enough to deal with the kde4 compilation issues.furanku wrote:Hmmm ... I've seen over the years much more unstable stuff, like broken system tools, in testing than an optional KDE4. So I can't really understand why not put it into portage. Mask it maybe if you think it will really "eat your children" (TM). But I always thought gentoo is for experienced users and all about choice?! Nobody wants to see it in stable or even think about making it the default, but how should it mature if testers wait for it appearing in "testing"? I know testing is for testing ebuilds ... but, hey, KDE4 had such a difficult birth, so give it some love!
That's what I actually do.i92guboj wrote:Yes, it's all about choice. You have the choice to use an overlay.
Calm down, why so aggresive? I did compile my SVN-KDE4 compilations by myself in the beginning. Hell, I did compile KDE pre1 versions myself. I make bug reports, provide patches if I can, I try to help others in the forums and on mailing lists. But I'm no developer. I'ld like to keep my system as clean as possible, and from my experience overlays cause more problems then official portage ebuilds, since they are not always in sync and you need to take care not to run into dependency problems.i92guboj wrote:If you aren't experienced enough to maintain an overlay you will not be experienced enough to deal with the kde4 compilation issues.
I don't know what you are talking about. I'm talking about official released KDE4.x packages.i92guboj wrote:We are not talking about ~arch stuff. We are talking about packages that, sometimes, do not even compile, and need continual care and patching.

KDE is a very large system. Just look at all the split ebuilds there are. This is not a simple "system tool". It's a complex desktop environment that has many dependencies and also many things that depend on it. All that needs to be tested first. From my understanding, the KDE4 overlay that is in unsupported was a test bed for the new KDE4 technology and their ebuilds. The ebuilds cannot go into portage until the official release of 4.0.0 which is tomorrow. I heard that the devs want the ebuilds in portage when 4.0.0 is officially released, or as close to it as possible. So, no fear, it will be there.furanku wrote:Hmmm ... I've seen over the years much more unstable stuff, like broken system tools, in testing than an optional KDE4. So I can't really understand why not put it into portage.

In the 4.0.0 tag on svn, that code is a little rough and there are patches that are needed to fix some bugs.furanku wrote:I don't know what you are talking about. I'm talking about official released KDE4.x packages.
I don't see anything aggressive on that words. At least, that was not my intention. I was just stating something that I believe it is true. And I also explained why I think that merging these packages into portage would not work. There might be simply no one willing to take responsibility over such a huge task.furanku wrote:Calm down, why so aggresive?i92guboj wrote:If you aren't experienced enough to maintain an overlay you will not be experienced enough to deal with the kde4 compilation issues.