Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PPA for Gimp 2.99 and GMIC?
#1
As per title. Kind of lost track, and DDG sends me to a PPA (mati75/gimp30) that isn't carrying the latest and greatest. Is there a PPA with 3.0 RC1? And one with GMIC?
Reply
#2
Hi ofnuts. I installed Gimp 2.99.18 yesterday into a Debian 'experimental' system.
I don't think Gimp 3 is released yet. The libs are Gimp 3.

I could only install to this testing system because it's compiled against the native libs.
I got it from here


   

I needed to use the Gimp libs which are complete. Some packs I downloaded and installed with 'sudo dpkg -i ' and some with 'sudo apt install'.
Reply
#3
Well, I had seriously lost track, because RC1 is not out yet. Good to know that there are debian package to support this, because if I need to recompile my own Gimp3, I may only have to recompile the main package.

Now currently busy transferring my own 2.10 to 24.04 with full Python support, so that will be next.
Reply
#4
The only way to have Gimp 2.10.38 with new Python 2.7 that I found is on ArchLinux and derivatives by compiling python2gimp (via yay / AUR) with some difficulty, but as far as I've managed, I can't get Gmic working.

The problem is having Gimp with Python2 installed, because in appimage there is only the IvanHC one which however has an old Python2 from Debian 10.

What I haven't tried is the one in Flatpak (genuinely developed by Gimp developers), so I don't know if python is there and what version it might be.

It ends up that to have new Python 2 and Gmic we have to use Windows. (in virtual machine? Wine?)

These days there have been changes at the scripting level in Gimp 2.99.19, but thanks to the appimages I have some different versions... and one at a time I fix the code.
Reply
#5
(10-28-2024, 12:51 PM)vitforlinux Wrote: It ends up that to have new Python 2 and Gmic we have to use Windows. (in virtual machine? Wine?)

So I've been running Windows unbeknownst to me...

   
Reply
#6
   


My G'MIC is a separate install via a deb from here.
I guess the python2 was challenging to roll into an appimage but it was worth it IMHO.
Reply
#7
@Tas_mania guess the python2 was challenging to roll into an appimage but it was worth it IMHO.

I prefer the older python2... there are old scripts that don't work on the new one
Reply
#8
(10 hours ago)vitforlinux Wrote: @Tas_mania guess the python2 was challenging to roll into an appimage but it was worth it IMHO.

I prefer the older python2... there are old scripts that don't work on the new one

You mean script that work on some early Pythonv2 and don't on 2?7?
Reply


Forum Jump: