This repository provides Unofficial AppImages of GIMP built on top of JuNest and the scripts to built them.
- GIMP flavors: what to choose?
- Usage
- About JuNest-based AppImages
- Troubleshooting
- About GIMP Stable for 32-bit systems
- Install and update them with ease
- Special credits
In this list, you will learn more about the five kinds of builds available in this repository.
GIMP "Stable" is the basic version built from the official Arch Linux repositorie (see https://archlinux.org/packages/extra/x86_64/gimp ).
If you have doubts about which one to use, I recommend you download this one.
Download it using the tags continuous-stable and latest:
- https://github.com/ivan-hc/GIMP-appimage/releases/tag/continuous-stable
- https://github.com/ivan-hc/GIMP-appimage/releases/latest
The build is updated every Sunday.
GIMP "Dev" is the upcoming version with all latest features and port to the more recent technologies.
To build this AppImage I've used the package "gimp-devel" from the Arch User Repository "AUR" (see https://aur.archlinux.org/packages/gimp-devel).
Download it using the tag continuous-dev:
The build is updated every three days.
GIMP "GIT" is built from source using the AUR package "gimp-git" (see https://aur.archlinux.org/packages/gimp-git). Every feature, even experimental, comes from source code, which may cause instability.
Download it using the tag continuous-git:
The build is updated every day.
GIMP "Hybrid" is based on the "Stable" version mentioned above, but in addition will contain support for the old Python2 and many third-party plugins.
To check the patches used, see Plugins patches for the "Hybrid" release.
"Hybrid" Is still a work in progress for GIMP fanatics!
If you are a GIMP fanatic too, you can rely on this build, alternatively rely on the official Flatpak which already has everything you are looking for.
This build is extremely experimental. USE AT YOUR OWN RISK!
If you really want use "Hybrid", download it using the tag continuous-hybrid
The build is updated every Sunday (one hour later "Stable").
The GIMP Stable and Developer versions based on the Ubuntu PPAs have a code base maintained by third parties, and are therefore obsolete and no longer maintained by me.
If you're constantly looking for updated builds, go with the first three options I've listed above.
If for some reason you prefer the Ubuntu base and PPAs, I recommend you fork this repository and redirect the Github Actions workflows to the dedicated scripts, as well scripts to build AppImages using a Debian base are avauilable here.
If you want to perform tests on my old builds, download them using the numbered tags (example 2.10.34-2.99.16, 2.10.32-2.99.14, 2.99.8-dev and 2.10.30)
- all of them are using this AppRun, this would help in case you want to build your own GIMP.
Personally, I will not build or distribute any more PPA-based versions of GIMP (click here for more details about my choice).
Once you have downloaded the AppImage, made it executable:
chmod a+x ./*.AppImage
Now you can double-click it or run it from the terminal (which lets you use hidden options).
For the Stable and Dev Edition builds based on JuNest, the inbuilt command "gimptool" is enabled as an option. To use it:
./*.AppImage gimptool [options]
You can also manually add plugins by placing them in the appropriate directories in $HOME/.config/GIMP.
See "3.1 Manual installation" at https://wiki.archlinux.org/title/GIMP#Plugins for more details.
“Hybrid” on the other hand is a work in progress that will be experimentally patched to contain all available plugins.
JuNest (Jailed User Nest) is a lightweight Arch Linux based distribution that allows the creation of disposable and partially isolated GNU/Linux environments within any generic GNU/Linux host OS and without requiring root privileges to install packages.
JuNest-based AppImages have more compatibility with much older systems.
Compiling these so-called "ArchImages" is easier and the Arch Linux base is a guarantee of continuity being it one of the most important GNU/Linux distributions, supported by a large community that offers more guarantees of continuity, as opposed to those based on PPA (which I stopped developing).
Learn more about ArchImage packaging at https://github.com/ivan-hc/ArchImage
You can analyze the AppImage by extracting them:
./*.AppImage --appimage-extract
edit the file ./squashfs-root/AppRun with your favourite text editor and remove the string 2> /dev/null. Save the file.
To start your tests, run the "AppRun" script like this:
./squashfs-root/AppRun
you can also rely on LD_DEBUG to find errors (learn more at https://www.bnikolic.co.uk/blog/linux-ld-debug.html), for example, look for missing libraries:
LD_DEBUG=libs ./squashfs-root/AppRun
I have also developed a 32-bit version of GIMP Stable built from the official Debian Stable repositories, for the old i386 architectures, see my other repository "ivan-hc/32-bit-AppImage-packages-database", you can download it from here.
I wrote two bash scripts to install and manage the applications: AM and AppMan. Their dual existence is based on the needs of the end user.
| "AM" Application Manager |
|---|
If you want to install system-wide applications on your GNU/Linux distribution in a way that is compatible with Linux Standard Base (all third-party apps must be installed in dedicated directories under /opt and their launchers and binaries in /usr/local/* ...), just use "AM" Application Manager. This app manager requires root privileges only to install / remove applications, the main advantage of this type of installation is that the same applications will be available to all users of the system. |
  |
| "AppMan" |
|---|
If you don't want to put your app manager in a specific path but want to use it portable and want to install / update / manage all your apps locally, download "AppMan" instead. With this script you will be able to decide where to install your applications (at the expense of a greater consumption of resources if the system is used by more users). AppMan is portable, all you have to do is write the name of a folder in your $HOME where you can install all the applications available in the "AM" database, and without root privileges. |
  |
- JuNest https://github.com/fsquillace/junest
- Arch Linux https://archlinux.org
