Hi,

Yemu writes:

is it possible to have gimp 2.0 and 2.1 installed together on one system? do binaries have different names (like it was with older gimp 1.2 and beta/1.3) thans for any suggestions cheers y

From the file INSTALL:

Since the plug-in API of GIMP 2.2 will be compatible with GIMP 2.0, 2.2 is supposed to install itself into the gimp-2.0 directories. It is thus not possible to install this development version into the same prefix with GIMP 2.0. A number of files will clash, so PLEASE USE A SEPARATE PREFIX to install this development version!!

Sven

Hi,

Yemu wrote:

is it possible to have gimp 2.0 and 2.1 installed together on one system? do binaries have different names (like it was with older gimp 1.2 and beta/1.3)

Yes, but not in the same prefix. gimp 2.2 is intended to replace gimp 2.0 - in fact the binary will continue to be called gimp-2.0 - and as such, some problems are found when installing both in the same prefix. However, you can have both installed under different prefixes. I have the GIMP 2.0.4 installed in /usr, and 2.1 from CVS in /usr/local/gimp-dev.

Cheers, Dave.

Accidentally sent this (by "Reply" instead of "Reply All") to Sven instead of the list ... (not very clever settings IMHO). Sorry Sven if you get it more than once.

Sven Neumann wrote:

>> It >> is thus not possible to install this development version into the >> same prefix with GIMP 2.0.

What does "prefix" mean? Does it mean "file system folder"?
Then why call it "prefix"?

Hi Andreas,

Andreas Waechter wrote:

Sven Neumann wrote:

It
is thus not possible to install this development version into the same prefix with GIMP 2.0.

What does "prefix" mean?
Does it mean "file system folder"?
Then why call it "prefix"?

The GIMP, like many programs, installs things in lots of folders. The binary goes in bin, but libraries go in lib, the headers go in include, the docs go somewhere in share, as do all the other data files.

The prefix is the directory which is prefixed to each of these. A prefix of /usr means that gimp-2.1 the binary ends up in /usr/bin, a prefix of /opt/gimp-dev means it'll be in /opt/gimp-dev/bin/gimp-2.1.

The configure script has a number of very common arguments it can take, and one of these is "--prefix=[directory]". I suggest that you run configure --help to see the full list of supported options - although in the GIMP that will be quite long. There are certainly things in there you didn't know about :)

Cheers, Dave.

On Thu, 09 Sep 2004 00:49:21 +0200 Andreas Waechter wrote:

Sven Neumann wrote:

>> It >> is thus not possible to install this development version into the >> same prefix with GIMP 2.0.

What does "prefix" mean? Does it mean "file system folder"?
Then why call it "prefix"?

You are using windows?

In a unixy system, Linux is most common I guess, the install process is;

1. Unpack the file

2. configure it

3. make it

4. install it

steps 2,3 and 4 are normally written as

./configure make
su make install

In the configure stage you can do all manner of configurations, the options available can be found by ./configure --help

One of the optios is where you will install it. eg ./configure --prefix=/opt

By custom, stable releases go to /usr as the default directory unstable go to /usr/local as the default directory

If you want to put another instance of the program, then you must specify another directory, can be anything as long as it is not /usr or /usr/local

/opt is as good as any other.

If you are going to be running dozens of instances then you might want to make a series of directories /opt/gimp-v1 /opt/gimp-v2 and use them as your install prefix, eg ./configure --prefix=/opt/gimp-v2 and everything will go there and won't clobber any of your other libraries.

HTH

Owen