grokking the gimp refers to what is now the development version, which is
stable enough for production and definately worth the effort to install.
if your using redhat 6.2 youll need to upgrade a few libs to try it, the
easiest way is just to get helix gnome, http://www.helixcode.com which
On Tue, 31 Oct 2000, pixel fairy wrote:
the development version, which is stable enough for production and
definately worth the effort to install.
Thanks to you and everyone else who has confirmed that.
if your using redhat 6.2 youll need to upgrade a few libs to try it, the
easiest way
its much easier to just get helix gnome and let it do all that for
you. then if you want to keep up with cvs, uninstall gimp and get that
from the cvs tree. when you update helix, it should only upgrade the
packages you still have leaving your home built gimp intact. (at least on
debian, ill have
'--prefix=' ./configure option when compiling from sources. To run the old
excutable just type
'/usr/bin/gimp'.
While this *might* work it is somewhat fragile. It's best to use completely
different prefixes for the two versions of the gimp (e.g. /opt/gimp-1.0 and
/opt/gimp-1.1), especially when yo
I seem to remember someone giving instructions on how to have and use
two versions of Gimp. I would like to use a 1.1 version for all of the
new and great things, but I would like to run a 1.0 version for all of
those great old and un-updated plugins (while I patiently wait for busy
developers
If the gimp executable is installed at '/usr/bin', and you compile the developer
sources then the
newer version should appear by default at '/usr/local/bin'. This can be changed with
the
'--prefix=' ./configure option when compiling from sources. To run the old excutable
just type
