Skip to content

"AM" 7.1
Compare
Choose a tag to compare
@ivan-hc ivan-hc released this 10 Jul 00:17
· 861 commits to main since this release
7.1
3447cc6
This commit was created on github.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

The beauty of DIY: building AppImages on the fly, like an AUR package!

Creating installation scripts for AppImages on the fly (option "-t" or "template", preference 1) is even easier now.

The two functions, assembly and installation, have been divided into two separate scripts:

  1. the installation script, which is the same as the AppImages (option "-t", preference "zero") will only have to intercept the package version (necessary for updates) and install the ready-made AppImage;
  2. the "assembly" script (with ".sh" extension) will be downloaded by the installation script into the temporary "tmp" directory created at the start of the installation process, so as to be executed and independently build the AppImage, before delivering it to the installation script.

To show you what I mean:

In this video we see how "calibre" is installed (note that a "calibre.sh" file is downloaded during the process):

calibre-installation-2024-07-10_01.46.59.mkv.mp4

In this video, I run the aforementioned "calibre.sh" script in a separate directory, in a completely standalone way:

calibre-standalone-2024-07-10_01.45.04.mkv.mp4

This method replaces the previous one which included both functions in a single body (and which led to the creation of scripts that were too long and complicated to manage).

NOTE, assembling AppImages on the fly can be a time-consuming and resource-intensive operation, depending on the size of the program you want to build.

I suggest contacting upstream developers to convince them to release official AppImage packages, or at least, create them on your own repositories using Github Actions, as I have done over the years.

On the other hand, the advantage of this method is that the update is continuous, using upstream packages and without being limited by the packager, be it official or third party.

You can upload other build scripts at https://github.com/ivan-hc/AM/tree/main/appimage-bulder-scripts

If you are a user of my AppImage creation tools

  • consider using AppImaGen, it is a simpler and more natural approach for this type of packages.
  • try NOT to use Archimage, as build times are longer and more resource intensive.
  • try NOT to use Snap2AppImage, it may be resource-intensive too, as Snap packages tend to be very large.

From the next release there should be suitable patches for other tools that use gcc, make and other software assembly systems.

Full Changelog: 7...7.1

Assets 2
Loading