I'd probably recomend waiting until the next release :-P . However if
you've struck a bug/missing feature in GLI that you can't work around
then you'll need to get the lastest code.
In general its easier for those wishing to keep up-to-date with bug
fixes, or if you want the lastest source code, to check-out GLI from
CVS. Whats in CVS may not be as stable as the beta release, but it will
take advantage of bug fixes. If you do checkout files from CVS remember
to run clean.sh before running makegli.sh
The other option, wherein I produce a tar/zip file containing compiled
fixed versions of offending code, is much trickier as several things may
have changed between the release and the current version, and I have to
try and include all of the necessary files (and so far I've managed to
get it right one out of three times, so I'm not batting so well). Also
there may have been changes to sundry files, view layouts, help files,
or even the way GLI is started, all of which complicate the issue. I
suppose the upside is that GLI doesn't need re-making, as the compiled
files are directly installed.
Greenstone Digital Library, University of Waikato
Jim Trott wrote:
>Do you recommend downloading patches from CVS?
>Knowledge Management Director
>Millennium Relief and Development Services