RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

Elle Stone
2014-01-24 19:58:14 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

I usually have three or four separate installations of Gimp from git, each in its own prefix.

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix, other than resetting the folder preferences every time I want to switch prefixes?

Elle

Liam R E Quin
2014-01-24 20:28:52 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On Fri, 2014-01-24 at 14:58 -0500, Elle Stone wrote:

I usually have three or four separate installations of Gimp from git, each in its own prefix.

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix, other than resetting the folder preferences every time I want to switch prefixes?

You could compile each to have its own preferences folder, e.g. when running autoconf or configure --with-gimpdir=.gimp-2.9-socks (say), and then you can configure their folders separately.

Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Elle Stone
2014-01-24 21:29:29 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On 01/24/2014 03:28 PM, Liam R E Quin wrote:

On Fri, 2014-01-24 at 14:58 -0500, Elle Stone wrote:

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix

You could compile each to have its own preferences folder, e.g. when running autoconf or configure --with-gimpdir=.gimp-2.9-socks (say), and then you can configure their folders separately.

Thanks! I'll give that a try.

Liam R E Quin
2014-01-24 21:54:57 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On Fri, 2014-01-24 at 16:56 -0500, Elle Stone wrote:

So there is no way to keep the gimpdir in the actual prefix? It will always be inside the hidden .config folder?

As far as I know that's the case.

At least that's better than all the prefixes using the same folder.

Yes.

Note, you can probably use symbolic links for the sub-folders like brushes, plug-ins, etc if it makes life easier.

Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Elle Stone
2014-01-24 21:56:37 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On 01/24/2014 04:29 PM, Elle Stone wrote:

On 01/24/2014 03:28 PM, Liam R E Quin wrote:

On Fri, 2014-01-24 at 14:58 -0500, Elle Stone wrote:

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix

You could compile each to have its own preferences folder, e.g. when running autoconf or configure --with-gimpdir=.gimp-2.9-socks (say), and then you can configure their folders separately.

Thanks! I'll give that a try.

Hmm, asking for --with-gimpdir=/home/elle/code/gimp291/run/gimpdir results in a folder located at:
/home/elle/.config/home/elle/code/gimp291/run/gimpdir

So there is no way to keep the gimpdir in the actual prefix? It will always be inside the hidden .config folder?

At least that's better than all the prefixes using the same folder.

Michael Natterer
2014-01-24 22:04:49 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On Fri, 2014-01-24 at 16:56 -0500, Elle Stone wrote:

On 01/24/2014 04:29 PM, Elle Stone wrote:

On 01/24/2014 03:28 PM, Liam R E Quin wrote:

On Fri, 2014-01-24 at 14:58 -0500, Elle Stone wrote:

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix

You could compile each to have its own preferences folder, e.g. when running autoconf or configure --with-gimpdir=.gimp-2.9-socks (say), and then you can configure their folders separately.

Thanks! I'll give that a try.

Hmm, asking for --with-gimpdir=/home/elle/code/gimp291/run/gimpdir results in a folder located at:
/home/elle/.config/home/elle/code/gimp291/run/gimpdir

So there is no way to keep the gimpdir in the actual prefix? It will always be inside the hidden .config folder?

Ouch, that is a bug. Passing an absolute path as gimpdir should use exactly that path of course. Would you file a bug please so this doesn't get forgotten?

thanks, --mitch

Elle Stone
2014-01-24 22:19:50 UTC (over 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On 01/24/2014 05:04 PM, Michael Natterer wrote:

On Fri, 2014-01-24 at 16:56 -0500, Elle Stone wrote:

Hmm, asking for --with-gimpdir=/home/elle/code/gimp291/run/gimpdir results in a folder located at:
/home/elle/.config/home/elle/code/gimp291/run/gimpdir

So there is no way to keep the gimpdir in the actual prefix? It will always be inside the hidden .config folder?

Ouch, that is a bug. Passing an absolute path as gimpdir should use exactly that path of course. Would you file a bug please so this doesn't get forgotten?

thanks, --mitch

Mitch, here's the bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=722939

Michael Schumacher
2014-01-26 20:15:16 UTC (about 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

Am 24.01.2014 20:58, schrieb Elle Stone:

I usually have three or four separate installations of Gimp from git, each in its own prefix.

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix, other than resetting the folder preferences every time I want to switch prefixes?

You could set the environment variable GIMP2_DIRECTORY to a different personal directory altogether, or set GIMP2_PLUGINDIR to point to a different plug-in location - see http://www.gimp.org/man/gimp.html#sect4 for more information about these variables.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
Elle Stone
2014-01-28 14:59:40 UTC (about 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

Recently I tried to update Gimp from git, which I've done quite a few times before without any problems. This time several things went wrong, the main symptom being that Gimp couldn't open a png file. I asked about the problem on IRC and several people came up with possible sources of the problem. Actually all the suggestions were correct! as there was more than one problem going on.

The most difficult issue to track down was related to libpng. I had recently updated Gentoo, which updated libpng. The updated Gimp was compiled using the new libpng. But when I tried to run Gimp, it used plugins from a previous installation (this is what took a long time to figure out), and of course those plugins were compiled using the old libpng library.

Tracking down exactly what was happening was not easy because I didn't realize that plugins were installed not only in the prefix but also in hidden home config folders.

Eventually I found and deleted the hidden home config folders and got Gimp in the first prefix properly installed, which created new hidden home config folders. Then I installed Gimp in a second prefix, and modified one of the plugins in the second prefix. But Gimp in the second prefix didn't see the modified plugin because it too was looking in the hidden home config folder, which it very politely didn't overwrite during the installation process.

I found the Preferences dialog for setting where to look for the various brushes, plugins, etc. That's a lot of folders to reset/reorder one by one! as the default order of where to look puts the hidden home config folder first.

So that is why I asked about convincing Gimp in a prefix to only use plugins installed in the prefix. Now that Mitch has fixed the "absolute/relative" path problem when using the configure option "--with-gimpdir=", each Gimp is only looking for plugins and etc in the specified folder inside the prefix. So that problem is solved, hopefully!

On 01/26/2014 03:15 PM, Michael Schumacher wrote:

Am 24.01.2014 20:58, schrieb Elle Stone:

I usually have three or four separate installations of Gimp from git, each in its own prefix.

Is there a way to tell Gimp in a prefix to only use the plugins in its own prefix, other than resetting the folder preferences every time I want to switch prefixes?

You could set the environment variable GIMP2_DIRECTORY to a different personal directory altogether, or set GIMP2_PLUGINDIR to point to a different plug-in location - see http://www.gimp.org/man/gimp.html#sect4 for more information about these variables.

The info on the page you reference is very interesting and I'm really hoping that the configure option "--with-gimpdir=" sets all of these folders to only look in the prefix-specific directory:

GIMP2_DIRECTORY to get the name of the personal GIMP directory. If unset .gimp-2.6 is used. If this is an absolute path, it is used as is. If it is a relative path, it is taken to be a subdirectory of the home directory. GIMP2_DATADIR
to get the base location for data files such as brushes and patterns. If unset /usr/share/gimp/2.0 is used. GIMP2_LOCALEDIR
to get the base location for translations. If unset /usr/share/locale is used.
GIMP2_PLUGINDIR
to get the base location for plug-ins and modules. If unset /usr/lib64/gimp/2.0 is used.
GIMP2_SYSCONFDIR
to get the location of configuration files. If unset /etc/gimp/2.0 is used.

Michael Natterer
2014-01-28 22:00:34 UTC (about 10 years ago)

Any way to convince Gimp installed in a prefix to only use the plugins in the prefix?

On Tue, 2014-01-28 at 09:59 -0500, Elle Stone wrote:

The info on the page you reference is very interesting and I'm really hoping that the configure option "--with-gimpdir=" sets all of these folders to only look in the prefix-specific directory:

The --with-gimpdir configure option *only* changes your personal gimp directory, the remaining directories are relative to --prefix and work perfectly fine since forever.

GIMP2_DIRECTORY
to get the name of the personal GIMP directory. If unset .gimp-2.6 is used. If this is an absolute path, it is used as is. If it is a relative path, it is taken to be a subdirectory of the home directory. GIMP2_DATADIR
to get the base location for data files such as brushes and patterns. If unset /usr/share/gimp/2.0 is used. GIMP2_LOCALEDIR
to get the base location for translations. If unset /usr/share/locale is used.
GIMP2_PLUGINDIR
to get the base location for plug-ins and modules. If unset /usr/lib64/gimp/2.0 is used.
GIMP2_SYSCONFDIR
to get the location of configuration files. If unset /etc/gimp/2.0 is used.
_______________________________________________ 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