Where is GIMP 2.10.18?

CVAlkan · 03-23-2020, 02:16 PM

I've downloaded the FlatPak for Gimp 2.10.18 and really like the new features and capabilities.

BUT: g'mic can't be made to work with the FlatPak version, and I want that back.

So far as I can determine, Otto K. has not updated his mainstay GIMP PPA for a while, and I can't locate any current Gimp deb file.

Short of compiling this myself, does anyone know what's going on with 2.10.18?

Thanks, and stay disinfected...

BW-userx · 03-24-2020, 09:33 AM

you could use a slackbuild to get this done, if you know how to figure out what you will not need in the slackbuild script so it will in fact install on your system. it isn't too hard to figure out, you can even use the hit and miss approach.

Like a lot of stuff down on the bottom

Code:

mkdir -p $PKG/usr/doc/gimp-$VERSION
cp -a \
  AUTHORS COPYING* HACKING INSTALL LICENSE NEWS README* docs/Wilber* \
  $PKG/usr/doc/gimp-$VERSION
( cd $PKG/usr/doc/gimp-$VERSION
  for i in \
    libgimp libgimpbase libgimpcolor libgimpconfig libgimpmath \
    libgimpmodule libgimpthumb libgimpwidgets ; do \
   ln -s /usr/share/gtk-doc/html/$i $i-html ; 
  done
)

# If there's a ChangeLog, installing at least part of the recent history
# is useful, but don't let it get totally out of control:
if [ -r ChangeLog ]; then
  DOCSDIR=$(echo $PKG/usr/doc/*-$VERSION)
  cat ChangeLog | head -n 1000 > $DOCSDIR/ChangeLog
  touch -r ChangeLog $DOCSDIR/ChangeLog
fi

find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG
/sbin/makepkg -l y -c n $TMP/gimp-$VERSION-$ARCH-$BUILD.txz

you will not need that.

https://mirror.slackbuilds.org/slack...urce/xap/gimp/

as far as dependencies you'll have to dig into that for yourself.

this is the approach I'd use instead of waiting for someone else to update there little repo. you can even look into how to create a deb and use that to keep track of your what is installed and easier to uninstall it.

CVAlkan · 03-24-2020, 11:23 AM

Uhhh, thanks, but I do know how to compile it. My guess, though, from the dead silence and absence of any "installable" packages after the big announcement of 2.10.18 (which happened about ten minutes after 2.10.16's release was found to have some major unidentified issue), makes me suspect that it will likely not compile successfully or run even if it does.

That's why I phrased the question as "Short of compiling this myself, does anyone know what's going on with 2.10.18?" The fact that it is only available as a FlatPak weeks after its release suggests that some unexpected upstream "fix" with gnome libraries or whatever has gummed up the works. The idea that the FlatPak seems to work but g'mic can't work with or isn't available for 2.10.18 reinforces that suspicion.

Given that Gimp is an app used by photographers, graphic artists, and similar pros and amateurs alike, and that it is and has been the premier open-source bitmapped graphics app for well over a decade, the idea that any significant percentage of the user base is capable of compiling from source seems quite unlikely. Gimp is also one of the major examples of what open-source has to offer, so I'm surprised that there seem to be no commentaries about this that I've run across.

Thus, it seems to me that something must be wrong in gimp-land, and I was curious if anyone might know what that was.

But, still, thanks for responding, and stay disinfected until Covid-19 gets updated to Covid-20 ☺.

BW-userx · 03-24-2020, 12:32 PM

I do not use it more then to just do little edits on images. nothing major. I do now I've been using
userx@userx-Archo:~$ sudo pacman -Ss gimp
extra/gimp 2.10.18-4 [installed]

and I have had no ill misgivings.

Mike_Walsh · 03-24-2020, 12:41 PM

@ CVAlkan:-

I don't know about 2.10.18; until very recently, I've been using 2.10.17.....but have, just today, updated to 2.10.19.

I run these as AppImages, if you know what those are. I get mine from aferrero's GIMP continuous-build page over at Github:-

https://github.com/aferrero2707/gimp-appimage/releases

There's a lot of listed releases on there, so to save you digging here is the direct link to the newest release with all plug-ins included:-

https://github.com/aferrero2707/gimp...86_64.AppImage

This appears to have been released only yesterday. You download these; make them executable; put them anywhere you want, and just click on 'em to run. It will create a config directory at /user/home/.config/GIMP-AppImage, and it should run in any Linux distro, since it contains absolutely everything required for it to run correctly. These unpack into /tmp for the duration of your session, and run from there.

These are big packages, admittedly, and won't suit everybody, since there is inevitable duplication of libs already present on your system in other locations (which to many seems totally pointless), but they ARE a very easy way of keeping the GIMP up-to-date with minimal 'messing-around'. Myself, I use this format a lot, since it's so easy to share these things between multiple OSs.

Just my two-penn'orth, FWIW.

Mike.

CVAlkan · 03-24-2020, 01:25 PM

Mike:

Thanks very much. I just downloaded it and ran it to confirm that it loads, etc. I guess I should have checked again today before posting.

I guess that, since gimp has gone from 2.10.16 to 2.10.19 in a matter of weeks, there was indeed something insidious going on, and I suppose we'll begin hearing the full story over the coming weeks (in between Covid-19 updates).

For others unfamiliar with the FlatPak format I mentioned, or the AppImage Mike mentioned, or the Snap packages Canonical is pushing, Mike's description *generally* applies to all of these in that they contain almost everything needed to run.

The conflict between the idea of sharing common elements across multiple programs and the idea of all-inclusive apps has been going on at least since the early 1970s and likely even earlier. In the world of personal computers, programs (what are called apps today) were all inclusive; for the most part you really couldn't run more than one at a time anyway. Later, with Windows, Microsoft took credit (as usual) for introducing the novel idea of sharing certain common functions among multiple apps, and introduced Dynamic Link Libraries (DLLs). Once non-Microsoft vendors naively began using these DLLs so they could concentrate on their own core functionality, Microsoft began changing the DLLs to accommodate refinements to its own software. Oops. So Windows PCs often ended up having the latest MS DLLs, as well as one or more older versions required for some other apps, and... This is where the term "DLL Hell" originated. Suffice it to say that there are good arguments for each general approach, but it's always a roll of the dice.

Now to go set up and test gimp 2.10.19 ...

Thanks again, Mike, for your response, and for making it educational for others.

Mike_Walsh · 03-24-2020, 02:00 PM

@ CVAlkan:-

No probs, m'man. I did notice one wee quirk when I was testing the newest version in 'pristine' trim; it appears to open 'full-screen', i.e., the workspace but without the side 'docks'.

(I say 'pristine' because in addition to sharing a single AppImage between 'Puppies', I also share the .config/GIMP-AppImage directory, too, using Pup's very powerful sym-link function - gets pressed into service in all sorts of unexpected ways, this does.....but we're known as an odd bunch in Puppy-land! - meaning that I can switch distros and just carry on from where I left off.)

For testing, I just temporarily deleted the sym-link, so upon startup it created a new config directory.....and that's when I noticed the 'oddity'. Replacing the sym-link to the common .config directory, everything appeared and worked as normal, so obviously YMMV. I would guess that if you've been using it for any length of time, you know how to make them re-appear anyway.....

BTW; what IS g'mic? I've heard of it, but never looked into it any further...

Mike.