Big news for KDE developers: KDE 4 is
nowgoing to be in /trunk. Update: I should have read the email better. As of this writing, no modules have actually be moved to trunk. Although the branch has already been created. Or in other words, /trunk isn’t KDE 4 quiet yet. Sorry for the confusion. Anways, KDE 4 will be in mainline development soon, with the upcoming KDE 3.5 now in a branch directory. The schedule seems to be still a bit undecided for 3.5, but now is the time to get your applications ported to KDE 4. ;-)
coolo mentioned kdesvn-build. I’m hoping it helps to make the transition easier as well. I’ll be frank and admit that I haven’t done much with KDE 4 and kdesvn-build at this point. I think what I may do is release an update to kdesvn-build (in /branches/KDE/3.5) as 0.97.1, making it default to downloading from 3.5 for now, while the version in trunk would remain unchanged (defaulting to /trunk). The only problem with that plan is that I believe the directory structure for 3.5 is slightly different, I may need to investigate and test on that before making the release.
I suppose now I have to setup a new KDE 4 build user. ;-)
Update: kdesvn-build 0.97.1 was released, containing the consolidated goodies over the last month of development, and defaulting to downloading KDE 3.5. If you plan on using kdesvn-build for KDE 4 development, please continue to use the version in trunk. From my basic testing it looks like everything should work fine if you’re using this for the initial checkout. Please file a bug if there’s something awry.