[Slightly OT] python based kdesvn-build variant that uses git locally available

Michael Pyne mpyne at purinchu.net
Sun May 25 21:59:49 BST 2008

On Sunday 25 May 2008, Michael Jansen wrote:
> On Sunday 25 May 2008 22:05:00 Michael Pyne wrote:
> > Other than that, make sure you architect it now so that you can run
> > update and build in parallel.  It took me awhile to get that into
> > kdesvn-build once the script was 8000 lines or so.
> I use kdesvn-build for a while now but never noticed it does that. Could
> you explain?

Normally kdesvn-build will perform the updates at first, one module at a time, 
and then after that is all done it will start with the builds, again with the 
modules in order.

I think it was 1.6 was the release where I added it, but basically kdesvn-
build will, as soon as a module has had its sources updated, will 
automatically start building the module at the same time, while all the rest 
of the modules continue to update.

Because Perl sucks I had to do it using inter-process communication instead of 
threading.  And because Perl IPC sucks I had to do that IPC using anonymous 
pipes instead of shared memory or something not retarded.  But it does seem to 

One side effect is that kdesvn-build now says "Waiting for source code update" 
instead of "Updating source" or whatever it used to say.  It also doesn't have 
a failed to update list (instead it goes into failed to build).  I should 
probably fix that latter point someday, I consider it a bug.

 - Michael Pyne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080525/f8958cbe/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080525/f8958cbe/attachment.sig>

More information about the kde-core-devel mailing list