github ivan-hc/AM 10.1
"AM" 10.1
on GitHub

12 hours ago

Towards Autonomy

This release increases the database to 3,019 applications in total (2,614 AppImages and 405 portable apps in other formats), 35 more than the previous release (with about ten removed).

This release features important new features, ranging from full autonomy, introducing its own PATH, on-the-fly AppImage creation, and support for portable2appimage.

Let's proceed in order.

Option -t

Creating install scripts for AppImages from GitHub will take into account AppImages distributed in archives (which is a serious violation of the standard, as AppImages themselves are "archives"... but many developers prefer to distribute them that way, and they're wrong). No more empty previews. You'll have to enter the appropriate keywords.

Additionally, a template for AppImages compiled on the fly has been added to include support for portable2appimage. Creating two scripts for that type of app will no longer be necessary.

#2231 #2236

Visit https://github.com/ivan-hc/portable2appimage for more info.

Option -u or update... and now also upgrade

You can now use the upgrade option to invoke -u or update as an alias.

by @fiftydinar in #2235 #2238

New custom PATH, for options -i or install and nolibfuse

Previously, if you didn't have appimagetool installed, it was downloaded every time you:

  1. installed an on-the-fly compiled AppImage (the -i or install option)
  2. converted old AppImages to the new runtime to remove the libfuse2 dependency (the nolibfuse option)
  3. updated both an on-the-fly compiled AppImage and one converted to the new runtime (see points 1 and 2 above)

From now on, this will no longer be necessary.

A new PATH has been launched for AM, which can be used while using the options above.

The only supported binary currently is appimagetool, but more are planned to be added in the future.

NOTE: You don't need to do anything; you don't need to modify any files. You just need to use the option that requires that specific binary.

The new PATH is volatile and cached. You can remove the binaries contained within it by running am -c or am clean, or by using an external tool set to clean the cache (e.g., Bleachbit).

This PATH, called "AMCACHEPATH," will only contain binaries authorized by AM. These will be removed if you have installed them and the command is present. For example, by running 

am -i appimagetool

In this case, the new PATH will not be considered.

Future Plans

With the new PATH, I want to allow greater coverage of necessary dependencies, if not installed. I aim to make AM much more autonomous, and I'm already working on other static binaries, strictly exported in AppImage format. The first is Busybox, which I'm still working on. You can help me improve it by contributing to the repository below:

https://github.com/ivan-hc/busybox-appimage

It will certainly be introduced in future releases of AM.

  • "AM" 10.1 - Custom PATH for appimagetool if not present by @ivan-hc in #2250

What's Changed

New Contributors

Full Changelog: 10...10.1

Check out latest releases or
releases around ivan-hc/AM 10.1

Don't miss a new AM release

NewReleases is sending notifications on new releases.

Get notifications