just connected a usb drive here to check whats on it, as KDE4 is so nice to show a small popup allowing me to directly open a file manager on the mounted disk I took the option. Turned out there is only 1 tar file on it. So I clicked on it and was presented with the nice “no app found for the mimetype, please select on”. After a quick run through the tree nothing showed up that would open tar files. Ok this machine has a rather limited kde4 installed (due to size constraints) so I quickly checked the trunk/KDE modules for possible archiving utilities. Found ark in kdeutils, but after building kdeutils it only presents me with rar and various zip formats.
Is this right? Don’t we have a single utility in trunk/KDE that can open up a tar archive? Or am I just blind? Can’t be that hard to use KTar from kdelibs, can it?
Well, back to my own world of a shell and the always-there “tar” utility🙂 Oh and off to filing a bugreport against ark of course😉
Update: Packagers seem to have fixed the problem, updates should be available soon. Thanks for the quick fix.
Hate to do this, but there’s been about 6 or 7 people now in #kdevelop and I’m not using kubuntu hence can’t test this myself.
To make a long story short: The Kubuntu packages of KDevelop4 Beta1 are (as of now, Friday January 6th, 21:00 PM CET) useless because either somethings missing in them or installed in the wrong directory. KDevelop doesn’t find any of its plugins and hence you can’t even create a new project, apparently running kbuildsycoca4 doesn’t help (according to the users that joined #kdevelop and tried it out). So its most probably not an outdated sycoca cache, but something else.
A bugreport with ubuntu has been filed and I hope the packagers can fix this soon, so kubuntu users can enjoy KDevelop4.
And to make that clear: I’m trying not to point fingers or blame anyone, mistakes happen. I’d just like to make sure this doesn’t have a negative effect on kdevelop4’s reputation because users start it, can’t do anything with it and then never look at it again.
PS: Would be nice if someone could post a short comment here when the packages are fixed so I can update the entry, I don’t want to sign up for a ubuntu-account just for that.
Yes, finally we managed to get the code into shape to do a first beta release of KDevelop4. See the dot article for some more information and where to get the source/binaries. The highlights are of course the awesome things David did for C++ support and the cmake support by Aleix.
On a side note: I’m also getting back to working on KDevelop4/win32, currently debugging some problems with DUChain. The good news is: Latest trunk already compiles and opens projects, the bad news: This is not part of the beta. I’m pretty confident though that the next beta will include win32 support.