"AM" 5.6.4

New option --force-latest, downgrade an alpha/beta/prerelease application from github, use the stable version and get updates only from "releases/latest".

Typically the installation scripts are directed to "releases" to allow downloading of the latest build available for GNU/Linux, if the developer has not uploaded one for the latest stable release.

USAGE (one app for time):

am --force-latest $PROGRAM

or

appman --force-latest $PROGRAM

This option searches for and replaces "releases" with "releases/latest" in the AM-updater script and launches the AM/AppMan command with the -u $PROGRAM option, so you can downgrade the app via update.

Furthermore, the AM-updater will always update only from "releases/latest"... hoping that the developer continues to develop for GNU/Linux or, in the case of AppImages, continues to build them, keeping the AppImage format alive, by supporting its existence (this is the true reason I whote "AM"/AppMan, afterall).

simplescreenrecorder-2024-02-08_06.18.17.mp4.mp4

See also https://github.com/ivan-hc/AppMan/issues/30 to see how this option is born.

"AM" 5.6.3

The installation process now shows download / progress without "less"

"AM" 5.6.2

New option "newrepo", add your custom repository.

USAGE:

am newrepo [URL]	# Set a new repository
am newrepo off		# Disable the custom repository
am newrepo on		# Enable the custom repository

EXAMPLE:

am newrepo https://raw.githubusercontent.com/IVAN-HC/AM-APPLICATION-MANAGER/main

• a message to remind you that the custom repository is active will be constant in every operation you do with "AM"/AppMan;

NOTE: This option is recommended for testing purposes only! Careless use of this option could cause irreparable damage to the system!

If you are unsure, don't use this option!

Rely only on the official repository of "AM" for daily use!

See #108

"AM" 5.6.1

Improved "-f" or "files" option!

Now sorts installed apps by size and shows if the app is an AppImage or something else.

"AM" 5.6

New "test" option, perhaps the one you were waiting for the most!

After creating your scripts with the -t or template option, have you ever wondered what it would be like to install the script using "AM" or AppMan?

Here is the test option, it is an extract of the -i or install option which instead of pointing to this repository, allows you to choose the path to a local file, even just by dragging the script into the terminal.

Patches are selected and applied depending on whether you use "AM" or "AppMan", just like a normal installation would.

USAGE:

am test /path/to/your-script

or just drag and drop the the script in the terminal, like this:

AM-5.6-option-test-usage.mp4

To remove the app, use the option -R, as always.

NOTE, I would like to point out that this option, being designed for testing purposes:

• works with one script at a time;
• the output does not use less -E, so you will see all unpatched messages, as you would with the dev option (previous release, 5.5);
• it is meant to work only with AM scripts that you can get using the -t option, be careful not to use different scripts, I have not made any security measures in this regard (yet).

You can consult the code of this commit for more information:
1410bab

Or stay up to date by following the "AM"/AppMan update history:
https://github.com/ivan-hc/AM-Application-Manager/commits/main/APP-MANAGER

I hope this option can be a turning point in making you participate in the development of "AM"/Appman and the growth of the database, which today has reached 1855 installation scripts for the x86_64 architecture.

"AM" 5.5

New option dev or devmode, view the installer output during installation.

USAGE:

am dev on

any reference to the command less -E will be removed.

To exit the "Developer Mode" use the command

am dev off

or use the command "am -s" or "am -u".

As always, users of "AppMan" must replace am with appman to use it.

"AM" 5.4

New option apikey to get unlimited access to https://api.github.com/ using your personal access tokens.

USAGE:

am apikey {Github Token} 

The configuration file named "ghapikey.txt" will be saved in '$AMPATH' .

Replace {Github Token} above with delete, remove or simply del to remove the file.

am apikey delete

Obviously users of "AppMan" must replace am with appman to use it.

This improvement will be rolled out to other options soon. For now it only works with convert (AppMan only) and install (both "AM" and AppMan).

Also see #104 for more details on how this option is born.

In addition to the new option, new code fixes have been added and several bugs have been fixed.

You can find all changes to the main CLI at the following url:

https://github.com/ivan-hc/AM-Application-Manager/commits/main/APP-MANAGER

---

About "AppMan"

Users of old releases that still point to https://github.com/ivan-hc/AppMan will download this transitional script. This is the content:

#!/usr/bin/env bash

################################################################################
#
# 			THIS IS A TRANSITION SCRIPT!
#
# Since version 5, "AppMan" and "AM" have been meged to share the same code.
#
# See https://github.com/ivan-hc/AM-Application-Manager/blob/main/APP-MANAGER
#
# This is a transition script that will download and rename the script above.
#
# So to make it work like "AppMan", "APP-MANAGER" will be renamed to "appman".
# 
# You will be able to run "AppMan" from the first moment you run this script,
#
# so you won't notice the difference with the real "AppMan" script.
#
# The method used by this transition script is the same of the "-s" option.
#
# For bug reports and feature requests in "AppMan", keep use this repository.
#
# New commits for the "AppMan"/"AM" code will be listed at the following URL:
#
# https://github.com/ivan-hc/AM-Application-Manager/commits/main/APP-MANAGER
#
################################################################################

DIR="$( cd "$( dirname "$0" )" && pwd )"

case $2 in
	*)
		wget -q https://raw.githubusercontent.com/ivan-hc/AM-application-manager/main/APP-MANAGER -O $DIR/appman && chmod a+x $DIR/appman
		cd $DIR
		exec ./appman "$@";;
esac

"AM" 5.3.1

This is a minor release which, compared to the "5.3" release, brings with it:

• refactoring the code (to simplify the analyzes of other developers who want to contribute) using functions;
• patch to ~/.bashrc and ~/.profile files to give ~/.local/bin the right priorities in $PATH (AppMan);
• verbose output about clean files and directories with "-c" option;
• the "-c" option can now remove orphaned launchers created with the "--launcher" option from ~/.local/share/applications/AppImages;
• the "-s" option will provide a direct link to the history of commits made on the main CLI "APP-MANAGER", in order to notify the user of all changes made to the code;
• various bug fixes and code cleanups.

"AM" 5.3

Run an AppImage in a sandbox using "Firejail"

New option --firejail or --sandbox, from now you can run AppImages using a sandbox (requires Firejail installed on the host).

USAGE:

am --firejail {PROGRAM}

At first start a copy of /etc/firejail/default.profile will be saved in your application's directory, so you're free to launch the AppImage once using the default Firejail profile (option 1) or the custom one (2), you can also patch the .desktop files (if available) to in sandbox-mode always (options 3 and 4). You can handle the custom firejail.profile file of the app using vim or nano using the option 5 (the first selection is vim).

Options 1, 2 and 5 are continuous to let you edit the file and test your changes immediately. Press any key to exit.

NOTE: once patched the .desktop files (options 3 and 4), they will be placed in ~/.local/share/applications, this means that if you have installed apps using AppMan, the original launchers will be overwrited.

AM-5.3.mp4

"AM" 5.2.1

Installation process:

• removed all error messages for missing optional dependencies;
• if among the apps you are installing there is any that requires optional dependencies, this will be skipped, moving on to the next one.

AM-5.2.1.mp4