Termux Packages

The update process follows a specific lifecycle to ensure stability and efficiency:

1. Pre-fetching: The tool identifies all packages to be processed and uses GraphQL (for GitHub) or Repology data to fetch the latest available versions in bulk.
2. Filtering: Packages are skipped if:
   • They do not have TERMUX_PKG_AUTO_UPDATE=true in their build.sh.
   • An open GitHub issue already exists with the label auto update failing for that package.
   • The package is already at the latest version.
3. Dependency Resolution: For any package requiring an update, the tool uses scripts/buildorder.py to find its dependencies and ensures they are updated first.
4. Execution: The termux_pkg_auto_update() function (defined in the package's build.sh) is called to perform the actual version upgrade logic.
5. Failure Handling: If an update fails during a GitHub Action run, the tool creates a new GitHub issue titled Auto update failing for <package_name> with the error logs included in a collapsible <details> block.

The calc package Makefile uses several variables to define the installation hierarchy. Most paths are relative to PREFIX. If you are building the package, you can override these variables to redirect the installation.

Key installation variables:

• PREFIX: The base installation directory. Defaults to /usr/local.
• BINDIR: The directory for executable binaries. Defaults to ${PREFIX}/bin.
• LIBDIR: The directory for libraries. Defaults to ${PREFIX}/lib.
• INCDIR: The directory for header files. Defaults to ${PREFIX}/include.
• CALC_SHAREDIR: The directory for shared data. Defaults to ${PREFIX}/lib/calc.
• MANDIR: The directory for man section 1 pages. Defaults to ${PREFIX}/share/man/man1.
• T: The top-level directory under which calc will be installed. This is set to ${DESTDIR} by default.

PREFIX ?= /usr/local
BINDIR= ${PREFIX}/bin
LIBDIR= ${PREFIX}/lib
INCDIR= ${PREFIX}/include
CALC_SHAREDIR= ${PREFIX}/lib/calc
MANDIR= ${PREFIX}/share/man/man1
T=${DESTDIR}

The update-packages script is highly configurable through environment variables. These allow you to control the build process, update logic, and automation behavior.

Build & Git Control

• BUILD_PACKAGES: If set to true, the script will attempt to build the updated packages.
• GIT_COMMIT_PACKAGES: If set to true, the script will commit changes to Git.
• GIT_PUSH_PACKAGES: If set to true, the script will push changes to the remote repository.
• CREATE_ISSUE: If set to true (and running in GitHub Actions), the script will create a GitHub issue if an update fails.

Update Logic

• TERMUX_PKG_AUTO_UPDATE: Set to true to enable auto-updates. Disabled by default.
• TERMUX_PKG_UPDATE_METHOD: Force a specific update method: repology, github, or gitlab.
• TERMUX_PKG_UPDATE_TAG_TYPE: Specify the tag type to use: latest-release-tag, latest-regex, or newest-tag.
• TERMUX_PKG_UPDATE_VERSION_REGEXP: Regexp used to extract the version with grep -oP.
• TERMUX_PKG_UPDATE_VERSION_SED_REGEXP: Regexp used to extract the version with sed.

Architecture & Platform

• TERMUX_ARCH: The architecture to test updates for (default: aarch64).
• GITHUB_TOKEN: Required for GitHub GraphQL API calls and interacting with GitHub issues via the gh CLI.

The termux_core__bash__set_shell_command_args_array function converts a shell-style command argument string into a properly formatted bash indexed array. It handles complex cases involving spaces and shell special characters by using xargs to ensure correct parsing.

Usage

termux_core__bash__set_shell_command_args_array <command_args_array_variable_name> <command_args_label> <command_args_string>

• <command_args_array_variable_name>: The name of the bash array variable to be populated.
• <command_args_label>: A label used for error reporting.
• <command_args_string>: The raw string containing the command arguments.

Behavior

• If the string contains only simple whitespace, it uses standard shell splitting.
• If the string contains shell special characters (e.g., ", ', *, ?, !, \[, \], +) or spaces that require quoting, it uses xargs to parse the arguments correctly.
• It validates that the xargs implementation in the current environment is capable of correct parsing before proceeding.
• It returns an error if the input string contains newline characters.

# Example: Converting a complex string to an array
my_args=()
cmd_str="'arg with space' 'arg with \"quotes\"'" 
termux_core__bash__set_shell_command_args_array my_args "my_command" "$cmd_str"

# my_args is now an array: ("arg with space" "arg with \"quotes\"")