When gimp is being configured with the --enable-default-binary options (which is
on by default since gimp-2.0rc), we create a symlink gimptool pointing to
gimptool-2.0. gimp-1.2 contains this symlink also, pointing to gimptool-1.2. The
intention was to make gimptool convenient to use for our users. There's a
problem however which is in the gimp-1.2 tree but since we can't fix it there,
we should think about possible workarounds in gimp-2.0.

The problem is that gimp.m4, which provides AM_PATH_GIMP(), the automake macro
to check for gimp-1.2 does not use gimptool-1.2 as it should. It checks for the
gimptool binary in the PATH and uses that. This means that if people have
gimp-2.0 installed, makefiles and configure scripts written to work with
gimp-1.2 start to break.

The gimp-print plug-in is a prominent example. If gimp-1.2 and gimp-2.0 are
installed and the gimp-print configure script is run, the script detects the
presence of gimp-1.2 but uses CFLAGS and LIBS from gimptool which points to
gimp-2.0.

Probably the only thing we can do about this is to not install the symlink and
to document that gimptool-2.0 needs to be used with gimp-2.0. This doesn't fix
all the systems that already have gimp-2.0.0 installed since the symlink exists
there already.