11-13-2024, 09:23 PM
Quote:gimp.org https://gitlab.gnome.org/GNOME/gimp/-/artifacts look for a working gimp-debian-x64 Look for 4 files / green tick against the name. It is well hidden.
Click on the browse icon (right-hand-side) then build -> linux -> _Output
Thanks rich for those good instructions. I made one this way but I think 'build' is a misnomer. 'Download' is more like it
The 3 links all use the same AppImage method. Here is a screengrab of the AppRun file:
You can see every path has to be exported otherwise the binaries can't find anything. I found exporting these paths is not needed. When you install software into Linux you don't have to export paths normally. The binaries already know where everything is because the Linux filesystem groups files where they belong. EG no libs in 'bin'.
AppImages are a completely self-contained filesystem just like the OS. They can also export symlinks as an executable (unlike tar gz which can only export symlinks)
I like how the Gimp git appimages use the correct homedir/.config/GIMP/3.0/ tree to store all user data. Ubuntu Snaps were just making their own user data locations which resulted in people losing their browser profiles.
For anyone updating scripts to Gimp3 I would use appimages rather than compiling.