Re: Another jhbuild libgsf glitch

[Jody Goldberg <jody gnome org>]

On Mon, Mar 24, 2008 at 10:32:06AM -0400, Prof J C Nash wrote:
> my attempt to set up a build-bot to allow for building of versions of 
> gnumeric that are up to date e.g., Windows cross-compile.
I've had a reasonable amount of success setting up a jhbuild based
win32 cross compile under debian based on arc's axcellent work.  The
moduleset and jhbuild files are in gnumeric/tools/win32.  The
process is not quite turnkey.

> My current problem concerns a matter that has appeared several times in 
> the archives, namely libgsf. The jhbuild default for building libgsf 
> creates 1.14.4, but the gnumeric.spec.in wants 1.14.6.

Sounds like two distinct issues.  The .spec file is largely out of
date as Morten pointed out, but it should not be the real issue.
Our configure.in is likely what's causing the problems, it too
requires 1.14.6.  The real problem, which is likely easy to fix, is
that jhbuild's deps are out of date.  I'd noticed they still pull in
gnomeprint and friends too.  It would be fairly simple to update the
req there.  A quick grep suggests
        jhbuild/modulesets/gnome-external-deps-*
are the right places to look to update the gsf req for jhbuild.
Alternatively we could just a custom module set and store it with
gnumeric akin to what we do for win32.

> There's also some glitchiness with scripts for gtk+: Here there appear 
> to be no "make" rules for install all or test all, but ignoring the 
> errors seems to be OK. However, I'm ultimately going to want to avoid 
> stoppages and manual intervention on these scripts.
That seems odd.  I've not seen that problem before.
 
> For information, my goal is to have a web page to select the settings 
> for the build and send an email notification when the result is done. 
> And I'm painfully aware that this will mean figuring out how to package 
> up everything so it works for other folk. Collaboration welcome -- this 
> sort of thing is not part of my computer background in numerical and web 
> programming.

As a start lets keep your build scripts in svn, and create a wiki
page with discussions of the issues you find.