Gimp-Forum.net
Gimp 3.0.0. rc1 AppImage - Printable Version

+- Gimp-Forum.net (https://www.gimp-forum.net)
+-- Forum: GIMP (https://www.gimp-forum.net/Forum-GIMP)
+--- Forum: Alternate Gimp packagings (https://www.gimp-forum.net/Forum-Alternate-Gimp-packagings)
+--- Thread: Gimp 3.0.0. rc1 AppImage (/Thread-Gimp-3-0-0-rc1-AppImage)

Pages: 1 2


RE: Gimp 3.0.0. rc1 AppImage - rich2005 - 11-13-2024

Some options for Gimp 3 RC1 , available at the moment, sizes and properties.

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
File size is 232 MB comes with python3(3.11.2) and script-fu Built on Debian. This is the one I am using with kubuntu 24.04 but not 22.04 (fails at least it does here)

ivan-hc https://github.com/ivan-hc/GIMP-appimage/releases in the Continuous Developer builds (JuNest Arch Linux-based AppImages) section.
File size is 207 MB Comes with python3(3.12.7) and script-fu Works with kubuntu 22.04 (not tried with anything earlier)

Artbox https://script-fu.github.io/artbox/hub/docs/folder/AppImage/ File size 245 MB Seems to be the gimp.org code with a couple of additions. It has python3(3.11.2) and script-fu.
For those interested in "the-workings" browse through the artbox folder https://script-fu.github.io/artbox/hub/docs/folder/ -> Guides / Plugins / Themes.


RE: Gimp 3.0.0. rc1 AppImage - Ofnuts - 11-13-2024

(11-13-2024, 06:13 AM)Tas_mania Wrote: I agree with rich the 'official' Artbox appimage is the one to use.

I noticed a few things.
The Gimp binary in the Gimp 3.00RC1 deb file is just 7.4Mb while the Gimp binary in the Artbox appimage is 35Mb.
The Gimp deb file is just a bare-bones Gimp but it contains python and script-fu and they are not listed as dependencies.
So a lot of differently compiled  Gimp3's.

I guess the documentation hasn't been done which is normal for FOSS Smile
It's hard not t call this version 'bloat ware'.

Why does it need a built-in LVM (logical volume management) and a gvfs virtual file system? The appimage is doing peer to peer encrypted internal networking. No wonder it took so long to make Smile

If you want to see how Artbox works check the AppRun file and see all the exported paths.
What would be good is a fully functional Gimp3 including python3 and script-fu in one package Smile

FWIW, the compilation of Gimp+Gegl+Babl on my Linux produces 190MB of artifacts with 14MB of executables (Gimp itself is about 9MB) and 39MB of libraries, but in the rest of the 190MB there are 45MB of docs and 52MB of of translations. The share directory is 33MB with 16MB of brushes and 9MB of icons. So the smallest delivery (Gimp+Resources+Translations)  is around 138MB (43MB compressed) or 86MB (26MB compressed) if you forego the translations.


RE: Gimp 3.0.0. rc1 AppImage - Tas_mania - 11-13-2024

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 Smile
The 3 links all use the same AppImage method. Here is a screengrab of the AppRun file:

[attachment=12595]

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.


RE: Gimp 3.0.0. rc1 AppImage - Tas_mania - 11-15-2024

I've spent some time today using the Gimp 3 appimage. With no python plug-ins it's unusable for animation and I noticed Script-Fu (Scheme) is broken. I see why Gimp needs networking - File option 'Send by Email'. I couldn't work-out if this sends your work as an XCF file but how many people would do that? Wouldn't you need to export and then send by email? I couldn't test this with no email client on this box. I did find It could open XCF's made with the previous Gimp 2.10. That's good.

I made this with Gimp3 Map Little Planet and made a sequence from the tilt slider. I had to finish it on Gimp 2.10.

[Image: MiniPlanetTilt36.webp]