Le 05/11/2012 19:35, Schindler Karl-Michael a écrit :
but I have the impression, that we still talking about slightly different things.
It seems so. To be clear, this is what I suppose people do: it is what is done for other systems.
1) If you are an end user, wanting to install grx from sources
- first install working copies of tiff, png, jpeg in proper place in your machine, if you want to use them in grx
- ./configure --prefix=/usr/local ...
- make
- su ... - make install
2) if you are a package manager, wanting to produce a binary package, change only the end as
-make DESTDIR=/SomeTempDir install
you will get a tree
/SomeTempDir/usr/local/ ... from which you produce a grx binary package containing only grx files in a tree rooted to /usr/local, not tiff, png, jpeg files.
I have introduced DESTDIR in grx 2.4.9 because it was requested by a SlackBuild package manager. This is now standard in GNU packages (it was not so when grx was first produced)
Now dependencies are taken into account by separate package managers such as Yum extender for linux or mingw-get for mingw32/msys If an user requests this manager to install grx, this software sees that it requires tiff, png, jpeg, install them first, then install grx, and refuse to install anything if this is not possible for some reason. In any case the files for tiff, jpeg, png are not contained inside the grx package.
Maurice