Using AppImages in Puppy...

[Mike Walsh]

Evening all.

Meant to mention this further back up the page, but the current 64-bit AppImage builds of the GIMP 2.10 (currently up to 2.10.19) can be found here, at Aferrero's GIMP continuous-build project page over at GitHub:-

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

As always; d/l, make executable, click to run. Simple. These contain everything required to fire-up, and just 'work'.

Enjoy.


Mike.

[rockedge]

Hello Mike Walsh,

around in my town they'd say "you're the man", thanks for the link for the gimp portable downloads

[Mike Walsh]

Hello Mike Walsh,

around in my town they'd say "you're the man", thanks for the link for the gimp portable downloads

Actually, I didn't find those through my own efforts. If I remember correctly, I obtained the link from an article over at OMG!Ubuntu!; it's a site I frequent for the very simple reason that there's a LOT of links to good stuff which will either work in Puppy straight-off, or with very minimal 'workarounds'. Being dedicated to current Ubuntu, it's usually a fair bet this stuff will work in the two flagship Puppies with minimal messing around.

And that often proves to be the case.

I've been using aferrero's GIMP AppImages for the last 3 or 4 releases. Since I'm satisfied by now that it 'does what it says on the tin', I thought it time to share the info.

Enjoy.


Mike.

[O.F.I.N.S.I.S.]

GIMP_AppImage-git-2.10.19-20200323-withplugins-x86_64

G'MIC plugin still crashing like in lots of previous versions.

GIMP without the G'MIC plugin is just a 50% of GIMP.

170 MB of download traffic for nothing...

[rockedge]

@O.F.I.N.S.I.S.

bummer....doesn't crash on my system, at least not yet

[gychang]

was able to use version 2.2.5 AppImage, works great, guess there is no recent version but will do on my Slacko64. Good information on this thread to rename to just darktable and use...

[O.F.I.N.S.I.S.]

Screenshot of G'MIC crashing.

[Mike Walsh]

@ O.F.I.N.S.I.S:-

Hm. I'm quite surprised; I had NO idea that a good part of the GIMP owes its existence to a little-known French expert on image processing with regard to medical scanners..... I'd heard of g'Mic, naturally, but never previously bothered to research it to any degree.

https://gmic.eu/tutorial/

You live & learn.


Mike.

[O.F.I.N.S.I.S.]

I'm using 2.10.8 without any issues on G'MIC. But it's not an AppImage. It's a .sfs file. I wasn't aware of this information about the "French Expert" also, but I like the FX possibilities of G'MIC very much. So, I'll stay with 2.10.8 from .sfs.

[rockedge]

Hello O.F.I.N.S.I.S.,

which link did you use to get the GIMP sfs? Could you share it again?

[O.F.I.N.S.I.S.]

Can't recall from where I got it or even if I built it myself from repositories.
I can only recall having another .sfs before that wich came as a "hidden" AppImage inside a .sfs file and was also crappy on G'MIC.

Uploaded to: https://workupload.com/file/nxTjTu6fqyE
Don't know how long it will remain for download since datafilehost.com is dead and I never used workupload.com before.

MD5: 656ba9aca65a9e830d4ffc1b78332236
SHA1: fd75e2aeb92f16314fecfd4f85d708d0332503ef
SHA256: 71ce42f66774d67e51dfc46036059275e52841490cad18fae5ce64dd9a21ff08
CRC32: 096df6ee

[rockedge]

Thank you O.F.I.N.S.I.S.!

I was able to download it!

[Mike Walsh]

I'm using 2.10.8 without any issues on G'MIC. But it's not an AppImage. It's a .sfs file. I wasn't aware of this information about the "French Expert" also, but I like the FX possibilities of G'MIC very much. So, I'll stay with 2.10.8 from .sfs.

TBH, it's not like there's any 'necessity' to have to upgrade the GIMP in any case. Some of my older Puppies still use 2.8, one even uses 2.6.....in every case, I'm still able to do everything I need to with them, so.....where's the need?

I just like to keep at least one Puppy up-to-date, that's all. (*shrug*)


Mike.

[O.F.I.N.S.I.S.]

You live & learn.

Yes, I hope I will be able to do so until my very last breath.

I was able to download it!

Cool.

TBH, it's not like there's any 'necessity' to have to upgrade the GIMP in any case. Some of my older Puppies still use 2.8, one even uses 2.6.....in every case, I'm still able to do everything I need to with them, so.....where's the need?

No need at all.

I'm just curious about new versions. No problem to stay with the 2.10.8. In my Tahr build I'm still using the 2.8.7 GimpPainter version - the one with the mypaint brushes. It has also a working G'MIC plus the wonderful beautify plugin.

Just missing this one in my newer GIMPs!

I could even use a 2.6 version if my new computer would be able to run the old Lucid version I got. Sadly this won't work anymore and I've had such a wonderful remastered version of that.

[O.F.I.N.S.I.S.]

Aahh, some search done and found a 64bit version from Ubuntu Xenial64 which seems to work in Bionic64.

https://launchpad.net/~hda-me/+archive/ ... /+packages
https://launchpad.net/~hda-me/+archive/ ... _amd64.deb

[fredx181]

Here's a simple command-line method to modify an existing appimage.
Can be handy in case an appimage doesnt work, e.g. because of missing libs.
It's very simple because an appimage is in fact an SFS, but "injected" with a binary "runtime", below commands use "runtime32" (for 32-bit), change to "runtime64" to create a 64-bit appimage (on a 64-bit OS)
The GUI program from here is using the same method of creating the appimage, but has more options (but not the option to extract an appimage, btw).

Let's assume that the appimage is in /root, replace "<originalappimage>" with the real name of the appimage.
Extract the appimage:

Code: Select all

/root/<originalappimage> --appimage-extract

A directory "squashfs-root" will appear.
Make your modifications inside, e.g. add missing libs or whatever.
Having done that, create a temporary squashfs file named "temp-squashfs.squashfs" from dir "squashfs-root":

Code: Select all

mksquashfs '/root/squashfs-root' temp-squashfs.squashfs  -root-owned -noappend

Extract the attached tarball "runtime.tar.gz" in root, then: (replace "<newappimage>" with preferred name)

Code: Select all

cat /root/runtime32 >> <newappimage> # change to runtime64 for 64-bit

Then create the new appimage by merging temp-squashfs.squashfs with <newappimage>: (use the same name as above for <newappimage>)

Code: Select all

cat /root/temp-squashfs.squashfs  >> <newappimage>

Make the new appimage executable:

Code: Select all

chmod a+x <newappimage>

That's it !

You may want to remove /root/temp-squashfs.squashfs and /root/squashfs-root:

Code: Select all

rm -f /root/temp-squashfs.squashfs
rm -fr /root/squashfs-root 

Fred

[Mike Walsh]

@ Fred:-

Nice idea, mate, but this method falls flat on its face in the Puppies, I'm sorry to say. The 'Dogs' must have stuff installed that's not native to Puppy itself.....which is a massive pain, because I really want to extract the Openshot AppImages and see just exactly what's inside the buggers!!


Mike.

[RedQuine]

I really want to extract the Openshot AppImages and see just exactly what's inside the buggers!!

Have you tried UExtract?

[fredx181]

Hey Mike,

@ Fred:-

Nice idea, mate, but this method falls flat on its face in the Puppies, I'm sorry to say. The 'Dogs' must have stuff installed that's not native to Puppy itself.....which is a massive pain, because I really want to extract the Openshot AppImages and see just exactly what's inside the buggers!!

Which Openshot AppImages ? (so I can try) Extracting appimages works on Puppy (no difference with 'Dogs') (from what I tested), note that you can only extract a 64-bit appimage on a 64 bit OS (and 32 bit only on 32-bit).

EDIT: Just tried extracing the appimage from here: https://www.openshot.org/nl/download/ and indeed doesn't work (unknown option --appimage-extract) which means to me that it's built with a different method than "normal". Btw, it doesn't run either (on BionicPup64).

EDIT2: It can be extracted with "AppimageExtract", so it's has been built the "old" way.
(maybe you still have the AppimageExtract binary, don't know atm where to find it, have to go out now, back later)

Fred

[Mike Walsh]

Morning, Fred.

RedQuine's hit the nail on the head (cheers, mate!). Jake (SFR)'s latest UExtract, v4.0, does indeed extract AppImages. I must thank Jake for that; I'd no idea that ability had been added into 'the mix' that UExtract was already capable of handling.....

Y'know, it's hardly surprising this is a strange one to get running. If you study the structure, J.T has gone and put absolutely everything into /usr/bin; binaries, libs, Python, Qt5, etc......the lot. I'm not even sure as it would be possible to re-build this into a working SFS package, for instance.....the construction is so peculiar. It's more like a kind of weird 'hybrid' of old and new.

----------------------------

One of the new guys, O.F.I.N.S.I.S, has uploaded some SFS packages from his own, highly-customized Bionicpup64, here (and subsequent posts):-

http://www.murga-linux.com/puppy/viewto ... 92#1054192

I've tried the final SFS - the biggest, all-in-one job - and yes, it does indeed run in a pristine Bionicpup64, OOTB. What we now need is someone with the patience of a saint (and extreme single-mindedness!) to disentangle the KDEnlive stuff from the Openshot stuff, hopefully resulting in a 'standalone' SFS of current, 2-series Openshot that anyone can just load, and it'll run.....

I don't think that someone is going to be me, somehow... (*shakes head*) Mikeslr, d'you fancy attacking this one with P.A.D.S and a copious supply of coffee...?

Interestingly, while this rather large SFS is loaded, giving you v2.4.1, the very latest AppImage - now up to v2.5.1 - will also run. If you unload the SFS, however, the AppImage doesn't want to know. What I always get is grumblings about missing Qt5 'version' info (?!??), along with a complaint about not finding the 'xdg-icon-resource'. (Huh??) I do not know what this last item is, although I do know from previous experience with older Openshots that every 'item' in the Python side of things seems to require matching with a system lib, and various python binaries.

I have to whole-heartedly concur with Mikeslr on this point; Python is a total bloody nightmare to work with! You can't even run an 'ldd' on it for missing stuff, 'cos Python is just a bunch of scripts.....apart from the framework binaries themselves, there are no individual binaries for it to work with.....

(*Jeez, Louise. Grrrrr.....* )


A very disgusted Mike.