+- Gimp-Forum.net (https://www.gimp-forum.net)
+-- Forum: GIMP (https://www.gimp-forum.net/Forum-GIMP)
+--- Forum: Gimp 2.10 (https://www.gimp-forum.net/Forum-Gimp-2-10)
+--- Thread: How to install GIMP for portable usage? (/Thread-How-to-install-GIMP-for-portable-usage)
Pages:
1
2
RE: How to install GIMP for portable usage? - rich2005 - 03-08-2018
Your first screenshot(s), you seem to have lost Python for some reason - do not know why.
That second link, well just a regular Gimp profile after a first run. Closing Gimp will populate that. see the video.
The shot of the 'portable' gimp profile. That is a bit mixed up installation. I am sure you know what goes where - leave you to sort that out.
![[Image: smn61zb.jpg]](https://i.imgur.com/smn61zb.jpg)
Error messages: I get error messages from my regular linux Gimp 2.9.9 - It does not like the old theme I use, it does not like recently-used.xbel disabled...etc Since it is not run from a terminal I tend to ignore these until something serious occurs.
The one I get with the Windows Gimp 2.9.8 is
(gimp-2.9.exe:2920): GLib-GIO-CRITICAL **: g_content_type_is_a: assertion ‘super type != NULL’ failed
And that gets repeated over-and-over-again on opening and saving an image. Bottom line. Does Gimp work? Yes. Ignore for the moment. It is a common type of error message in all sorts of linux applications and some ported to Windows.
Everyone has their own way of doing things but in this case as I wrote earlier, keep things simple. When it is working that is the time to tuck files and folders away under long paths.
This video shows much of the above: https://youtu.be/CT3vuEBKkIY duration 5 minutes
I would consider that a working installation.
RE: How to install GIMP for portable usage? - ajax - 03-09-2018
Sorry for delayed response. I've been without Internet for more than a day.
It looks like I caused some, if not all, of the problem. When I undertook my experiment I created the folder that was referenced by the variable GIMP2_DIRECTORY whereas the comparable folder did not exist when doing the normal startup. However, if this folder is also removed for the portable case then the startup looks the same and the fairly large set of empty folders are created. Also the console messages look identical. Therefore, I’m guessing that what could be triggering the creation of these folders, previously missing on startup, is that GIMP fails to find the applicable folder. The one slight difference that remains is that in the portable case (i.e., using GIMP2_DIRECTORY rather than default) the sub-folder named “2.9” is not created. Guessing again about the logic makes me think that when default is used GIMP contemplates the possibility for multiple, possibly incompatible, versions of GIMP to be sharing this directory and so the one named “2.9” is created to preserve integrity in such a case. When the user overrides the default the idea is to put it where the user requested.
At this point the portable case looks good even though I must admit that not much usage of GIMP has occurred yet. Therefore, I’m very grateful for the assistance that Rich provided. I wouldn't have gotten this working otherwise.
This does lead to another question but I'm thinking that belongs in another post.
Just in case this matters to anyone else I’ve attached the script that I now have working. I hope it is commented well enough to explain what needs to be done to use it. Apparently this site won't allow attachments with the .js file extension therefore I've appended .txt which must be removed to use the script.
THANKS to RICH