Skip to content

5.0

Choose a tag to compare

@Azathothas Azathothas released this 26 Oct 01:05
· 86 commits to main since this release
bdea101

This release brings several new features.

Experimental support for Anylinux Sharun-based AppImages has been introduced

A NEW-anylinux.sh script has been added, which basically uses JuNest to install the application on Arch Linux, but actually uses Sharun to extract the libraries and build the AppImage.

AnyLinux AppImages are designed to run seamlessly on any Linux distribution, including older distributions and musl-based ones, without the need of a container, on the contrary of my classic Archimages.

To learn more, see https://github.com/pkgforge-dev/Anylinux-AppImages

The script is still in the experimental stage, improvements will be made in the coming months.

To test it, press "2".

Leave blank or press "1" if you want to create an Archimage, as always

Istantanea_2025-10-22_00-57-36

Using Sharun to collect libraries

The NEW-junest.sh script now also uses Sharun, but only to compile the Archimages, gathering libraries, launching the app (if necessary) isolated in the script's temporary HOME directory, and locating as many libraries as possible.

The resulting Archimage will, in most cases, be ready to use on the first try. The success rate is higher!

Abiword.Archimage.5.0.mp4

NOTE, the video was shot during early testing, which did not yet include the introduction of archimage-builder.sh, see below.

Reduced Archimage script

The NEW-junest.sh script is now less than 200 lines long.

All core processes run in a dedicated module: archimage-builder.sh

This centralization will allow for the timely maintenance of multiple Archimages simultaneously, should drastic changes to the Arch Linux base be introduced.

During startup, the aforementioned module will also be downloaded, containing the core operations for:

  • installing programs in JuNest
  • identifying the launcher and icon
  • scanning libraries
  • streamlining the final product
  • creating mounting points.

In the user script appname-junest.sh, you can add:

  • the app name
  • binary
  • dependencies
  • keywords to add/remove
  • additional mounting paths
  • additional mirrors and repositories
  • enabling Nvidia support
  • additional custom commands after each process
  • the final part of the AppRun with custom functions and commands (or leave defaults)
  • data related to the reference repository, including update info

The new archimage-builder.sh will be downloaded at start, in the root of the working directory

All in less than 200 lines, without frills.

Each section also has a clear description to guide you if you have any questions about modifying the script.

simplescreenrecorder-2025-10-26_00.28.03.mp4

Conclusions

This release aims to simplify the readability of the scripts, their configuration, and the centrality of its build system.

Arch Linux is subject to changes, sometimes drastic and unexpected, which easily lead to the breaking of some links and libraries necessary for the functioning of an Archimage.

Personally, as of this writing, I have about 40 Archimage packages scattered across my repositories, and many of them have their own repository.

I needed to simplify my life by keeping track of my various repositories, so I decided to separate the main script into a highly configurable part for the user (the NEW-junest.sh script) and a part dedicated to the build (archimage-builder.sh), from which it will be possible to intervene as the most unwelcome changes become apparent.

I hope you enjoy this release. See you next!