Ken Moffat wrote: > On 7 March 2010 11:37, Matthew Burgess <[email protected]> wrote: >> Hi all, >> >> I know a couple of folks here have built KDE recently. I think I >> already know the answer to this, but I think I have to grab kdesupport >> out of SVN in order to build KDELibs, right? My conclusion was arrived >> at because kdelibs wants 'automoc4' from kdesupport but there is no >> kdesupport tarball available from KDE's download site. >> > > Not recent, but when I was building kde4 I used to grab source tarballs > from e.g. Arch. A quick google suggests Slackware have > automoc-0.9.88.tar.bz2 (failing tarballs, there's always rpm2cpio). > At that time, I grabbed phonon from debian, looks as if qimageblitz > maybe had a proper release. Looked as if a version gets tagged in > svn from time to time, but tarballs aren't prepared. > >> If that's the case, how do I stop things like oxygen-icons being built >> that already have their own tarballs available? Preferably I don't even >> want to check out the oxygen-icons area of svn but I'm not sure that's >> possible...an 'svn update' on such a checkout would pull oxygen-icons >> next time around anyway, I would have thought. > > Don't know, and I'm afraid I don't care - building software became > a lot easier when I gave up kde4 and cmake.
I'm seriously considering giving up on it too, to be honest. The cmake output clearly stated that I needed to use automoc from kdesupport, but now folks are pointing me at old automoc tarballs. If the dev's can't even be bothered to update their dependency documentation then it doesn't bode well for the rest of what I might encounter. Various howtos I've found on the net also point at pulling phonon from git, and various other bits from their respective SCM repositories. That's not for me, I'm afraid. How on earth upstream devs cope with bug reports when they've no way of controlling/repeating what their users might be linking against I've no idea. Following on from the earlier thread discussing lightweight window managers/desktop environments, I'm currently trying to get lxde put together. lxdm requires consolekit which requires polkit which requires PAM. Despite polkit accepting '--with-authfw=shadow' it bails as there are assumptions all over the code on PAM being present. What was it I said above about developers accurately detailing their dependencies :-). Aside from that though, I think lxde might be just what I'm after! Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
