Well #arrogance mode on # what about some Bash (or shell) basics #arrogance mode off #
for example
according to your real path . put it in your ~bashrc maybe or into a rc.d or profile.d script, wherever you prefer to have it

But what about the Order for Kde main packages ? (for svn from today 11/jan/09)
I tried
-prereqs all (or most) optional ones also
- qt (without phonon)
- kdesupport ( we get phonon here , don't build the 2 , cmake will complain)
- kdelibs
- kdepimlibs
- kdebindings (get stuck about all this smoke stuff)
- kdebase (installed kerberos and pam , but actually don't know if that was a good idea?!)

kdebindings won't compile because in php-qt dir cmake is missing
the smoke subdir, even when I switch all smoke stuff off .

There is a build.sh in there which generates the dir but then kdebindings won't configure/compile anymore because the targets already exist , but with smoke switched off cmake doesn't complain about the missing dir anymore but obviously won't install the already build targets. a make install in that dir doesn't work --- Thats quite strange - any ideas ?

kdebase fail on plasma for the moment ....
Or do I have to build ~bindings after ~base (I read somewhere to build them before but all other doc says to do ~base before )
Someone already succeeded to build kde svn on slack 12.2 ??

I built KDE 4.1.96 which is only a few days old (in fact it is tagged 4.2RC1), but I did not use kdesupport and instead used to pick the relevant deps from that tarball. At this moment I only use qimageblitz, eigen2 an automoc4 from a kdesupport snapshot (r900905).
The build order of the KDE packages (some of the ones at the end are from extragear) that I used is:
For kdebindings I had to use a small patch in order to let 4.1.96 compile:
Other than that, no real problems, but is it very important that you have the very latest releases of all the dependencies!

Eric

I was finally able to successfully compile it. I used the one from trunk.

You should be aware that since last Tuesday, if you download directly from trunk you are getting what will soon be KDE 4.3, since 4.2 has been branched already.

Tagging the tree with 4.2 has nothing to do with a release of 4.3 any time soon. KDE4.3 is scheduled for release on july 28th, 2009.

What you will soon see as an official release is KDE 4.2 (the 4.2 tag means that only bugfixes are allowed now for 4.2).

Eric

I think what he meant is that since kde 4.2rc1 has been tagged, trunk is no longer the development tree that will eventually lead to kde 4.2. In fact trunk is open for new features already, targeting kde 4.3. So if anyone wants a newer snapshot of kde 4.2, trunk is no longer the place to get it from.

Yes that was exactly what I meant. Thanks for clarifiying that.

This was my source just in case anybody is interested: http://aseigo.blogspot.com/2009/01/4...is-now-43.html

Cheers

I finally finished compiling right now from branch.
Kdebindings is still missing smoke-stuff - but compiles when I leave out all smoke and php-qt stuff, there might be some deps missing