Hi Elle,

On Mon, 10 Mar 2014 11:44:23 -0400 Elle Stone wrote:

I update three separate copies of babl/gegl/gimp from git, each in a prefix, on average once a week.

Other than reading the git logs, is there an easy way to check to see whether software requirements (png, tiff, glib, etc) have been bumped up?

Also, I've been updating command by command in a virtual terminal and my computer isn't very fast. I'd like to write a script that executes all the commands all at once, but exits with an informative error message printed to screen as soon as something doesn't configure, compile, or install properly. Does anyone have such a script or know how to write one?

This should be doable with a script written in Shell, Perl 5, Python, Ruby, etc. by inspecting the status exit code of the command.

E.g: in Bash:

if ! ./configure $PARAMS > configure.log 2>&1 ; then echo "Configure command failed"
exit -1
fi

(Untested!)

There may be a ready made solution, but writing something quick yourself would probably be less time consuming.

Regards,

Shlomi Fish

-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
Chuck Norris/etc. Facts - http://www.shlomifish.org/humour/bits/facts/

I also have versions of this code in COBOL.NET, Intercal, PDP‐10 Assembly, J,
APL, Windows NT 4.0 Batch script and Autocad Lisp — I’m sure you can handle
all of them because none of them is Perl. ;-).

Please reply to list if it's a mailing list post - http://shlom.in/reply .

Here are two scripts that I use to help keep git up to date. The first updates my git checkouts, and the second cleans out any build files (which is useful to run from time to time). They require $SRC_DIR to be set to the directory that your babl/gegl/gimp checkouts are under, and $INSTALL_PREFIX must be the location of your install prefix.

The main key to these script is that the first line is "#!/bin/bash -e". The -e argument to bash means that if any command in the script fails, then the script will exit immediately, instead of continuing to the next command.

upd.sh:

#!/bin/bash -e

build () { cd $SRC_DIR/$1

git pull --rebase

if [ ! -f ./Makefile ]; then
./autogen.sh --prefix=$INSTALL_PREFIX --enable-fast-install $2 fi

make
make install
}

build babl
build gegl "--enable-gtk-doc --enable-debug" build gimp

clean.sh:

#!/bin/bash

rm -r $INSTALL_PREFIX mkdir $INSTALL_PREFIX

clean () { cd $SRC_DIR/$1
git clean -Xdf
git pull --rebase
}

clean babl
clean gegl
clean gimp

Hopefully this helps.

-- drawoc

On Tue, Mar 11, 2014 at 7:37 AM, Elle Stone wrote:

Shlomi Fish and SorinN,

Thanks! With examples to work from, hopefully it won't be too hard to write a script that makes updating GIMP easier.

Elle

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list