kdesvn-build konversation
December 10th 2009 07:52 pm
Now Konversation has also switched to git.
Peter mentioned it being unfortunate that there was not a way to build Subversion and git modules with the same tool. Except that there is, and has been since October (and even before in the summer if you like unreleased code). kdesvn-build. Yes, I know I still need to rename it, I’ll get to that eventually ;)
Anyways, here’s what I added to my existing kdesvn-buildrc to build konversation:
module konversation
repository git://gitorious.org/konversation/konversation.git
branch master
end module
Now one catch is that scripts (including Michael Jansen’s build tool, last I’d heard) seem to have less success running git than doing so at the command line :-(. If you do end up manually cloning the git repository then make sure you’re using the trunk version of kdesvn-build to avoid git errors later.
One possible workaround is to use the HTTP protocol for the repository instead of the git:// version, but that’s less efficient so I’d really prefer to find a way to make git always work from scripts instead.
Anyways, congrats to the Konversation developers on continuing to blaze the git trail for KDE.
Thanks! :)
Do we have any idea why git malfunctions inside scripts? I’ve been experience this issue for some time (trying to package “latest-git” PKGBUILDs for Archlinux) and didn’t realize this was well known behavior.
Does kdesvn-build already reflect the change of the kdevelop path?
atomopawn: Not sure, I suspect something related to either PTY handling or env variables. Running git under the expect module or some other PTY-using code might help narrow it down.
Christoph: With certain exceptions regarding default path searching based on module name, kdesvn-build just downloads what you tell it to. You should be able to download and build kdevelop right now (since you are specifying the path to it after all).