bauh | Graphical user interface for managing your Linux applications. Supports AppImage, Arch packages (inc

If you prefer an isolated installation from the system libraries, type the following commands:.
fuse: the package name may vary from distribution
Download the .AppImage file attached with the latest release from https://github.com/vinifmor/bauh/releases.
Run the following command through a terminal: chmod a+x bauh-${version}-x86_64.AppImage (replace ${version} by the respective downloaded version)
Launch it: ./bauh-${version}-x86_64.AppImage
timeshift: system backup
aria2: multi-threaded downloads
axel: multi-threaded downloads alternative
libappindicator3-1: tray-mode
wget, sqlite3, fuse: AppImage support
flatpak: Flatpaks support
snapd: Snaps support
python3-lxml, python3-bs4: Web apps support
python3-venv: isolated installation
timeshift: system backup
aria2: multi-threaded downloads
axel: multi-threaded downloads alternative
libappindicator-gtk2: tray-mode (GTK2 desktop environments)
libappindicator-gtk3: tray-mode (GTK3 desktop environments)
wget, sqlite, fuse2, fuse3: AppImage support
flatpak: Flatpak support
snapd: Snap support
pacman: ArchLinux package management support
python-lxml, python-beautifulsoup4: Web apps support
python-venv: isolated installation
Copy the files from bauh/desktop to ~/.local/share/applications (or /usr/share/applications for root)
Replace the Exec field on theses files by the bauh binary path. e.g: Exec=/usr/bin/bauh (or bauh_env/bin/bauh)
Copy logo.svg to /usr/share/icons/hicolor/scalable/apps as bauh.svg
Supported sources: AppImageHub (applications with no releases published to GitHub are not available)
All available application names can be found at apps.txt
Only x86_64 AppImage files are available through the search mechanism at the moment
Crashes may happen during an AppImage installation if AppImageLauncher is installed. It is recommended to uninstall it and reboot your system before trying to install an application.
Extra actions Install AppImage file: allows to install an external AppImage file Upgrade file: allows to upgrade a manually installed AppImage file Update database: manually synchronize the AppImage database
Installed applications are store at ~/.local/share/bauh/appimage/installed (or /usr/local/share/bauh/installed for root)
Desktop entries (menu shortcuts) of the installed applications are stored at ~/.local/share/applications (or /usr/share/applications for root). Name pattern: bauh_appimage_appname.desktop
Symlinks are created at ~/.local/bin (or /usr/local/bin for root). They have the same name of the application (if the name already exists, it will be created as 'app_name-appimage'. e.g: rpcs3-appimage)
Downloaded database files are stored at ~/.cache/bauh/appimage (or /var/cache/bauh/appimage for root) as apps.db and releases.db
Databases are updated during the initialization process if they are considered outdated
The configuration file is located at ~/.config/bauh/appimage.yml (or /etc/bauh/appimage.yml for root) and it allows the following customizations:
Applications with ignored updates are defined at ~/.config/bauh/appimage/updates_ignored.txt (or /etc/bauh/appimage/updates_ignored.txt for root)
Only available for Arch-based systems
It handles conflicts, missing / optional packages installations, and several providers scenarios
rebuild-detector integration (AUR only)
Automatically makes simple package compilation improvements (for AUR packages): a) if MAKEFLAGS is not set in /etc/makepkg.conf, then a copy of /etc/makepkg.conf will be generated at ~/.config/bauh/arch/makepkg.conf defining MAKEFLAGS to work with the number of your machine processors (-j${nproc}). b) same as previous, but related to COMPRESSXZ and COMPRESSZST definitions (if '--threads=0' is not defined) c) ccache will be added to BUILDENV if it is installed on the system and already not defined d) set the device CPUs to performance scaling governor Obs: For more information about them, have a look at Makepkg
Extra actions Synchronize packages database: synchronizes the database against the configured mirrors (sudo pacman -Syy) Refresh mirrors: allows to define multiple mirrors locations and sort by the fastest (sudo pacman-mirrors -c country1,country2 && sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syy) Quick system upgrade: it executes a default pacman upgrade (pacman -Syyu --noconfirm) Clean cache: it cleans the pacman cache directory (default: /var/cache/pacman/pkg) Mark PKGBUILD as editable: it marks a given PKGBUILD of a package as editable (a popup with the PKGBUILD will be displayed before upgrading/downgrading this package). Action only available when the configuration property edit_aur_pkgbuild is not false. Unmark PKGBUILD as editable: reverts the action described above. Action only available when the configuration property edit_aur_pkgbuild is not false. Allow reinstallation check: it allows to check if a given AUR packages requires to be rebuilt Ignore reinstallation check: it does not to check if a given AUR packages requires to be rebuilt Check Snaps support: checks if the Snapd services are properly enabled. Reinstall (AUR only): rebuilds an installed package.
If you have AUR added as a repository on you pacman configuration, make sure to disable bauh's support (through the settings described below)
AUR package compilation may require additional installed packages to work properly. Some of them are defined on the field optdepends of the PKGBUILD for a root user the following additional applications must be installed: useradd: required to create a simple user named bauh-aur (since makepkg does not allow building packages as the root user) runuser: required to run commands as another user
Repository packages currently do not support the following actions: Downgrade and History
If some of your installed packages are not categorized, open a PullRequest to the bauh-files repository changing categories.txt
During bauh initialization a full AUR normalized index is saved at ~/.cache/bauh/arch/aur/index.txt
Installed AUR packages have their PKGBUILD files cached at ~/.cache/bauh/arch/installed/$pkgname
Packages with ignored updates are defined at ~/.config/bauh/arch/updates_ignored.txt
The configuration file is located at ~/.config/bauh/arch.yml and it allows the following customizations:
Applications with ignored updates are defined at ~/.config/bauh/flatpak/updates_ignored.txt
The configuration file is located at ~/.config/bauh/flatpak.yml and it allows the following customizations:
Make sure snapd is properly installed and enabled on your system: https://snapcraft.io/docs/installing-snapd
Extra actions: Refresh: tries to update the current Snap application revision Change channel: allows to change the Snap application channel
The configuration file is located at ~/.config/bauh/snap.yml and it allows the following customizations:
It allows the installation of Web applications by typing their addresses/URLs on the search bar
It offers the possibility to customize the generated app the way you want:
It provides some suggestions coming with predefined settings, and they also can be found by their names. They are defined at suggestions.yml, and downloaded during the application usage.
It relies on NodeJS, Electron and nativefier to do all the magic, but you do not need them installed on your system. An isolated installation environment will be generated at ~/.local/share/bauh/web/env (or /usr/local/share/bauh/web/env for root).
It supports DRM protected content through a custom Electron implementation provided by castLabs. nativefier handles the switch between the official Electron and the custom.
The isolated environment is created based on the settings defined in environment.yml (downloaded during runtime).
Some applications require Javascript fixes to properly work. If there is a known fix, bauh will download the file from fix and attach it to the generated app. The fix files are saved on the disk following the pattern ~/.local/share/bauh/web/fixes/electron_{branch}/{app_name}.js (or /usr/local/share/bauh/web/fixes/... for root)
The installed applications are located at ~/.local/share/bauh/installed (or /usr/local/share/bauh/web/installed for root).
A desktop entry / menu shortcut will be generated for the installed applications at ~/.local/share/applications (or /usr/share/applications for root)
If the Tray Mode Start Minimized is defined during the installation setup, a desktop entry will be also generated at ~/.config/autostart (or /etc/xdg/autostart for root) allowing the application to launch automatically after the system's boot attached to the tray.
Extra actions Clean installation environment: removes all the installation environment folders (it does not remove installed apps)
The configuration file is located at ~/.config/bauh/web.yml (or /etc/bauh/web.yml for root) and it allows the following customizations:
--tray: if bauh should be launched attaching itself to the system tray.
--settings: it displays only the settings window.
--reset: it cleans all configurations and cached data stored in the HOME directory.
--logs: it enables logs (for debugging purposes).
--offline: it assumes the internet connection is off.
System administrators and package managers of Linux distributions can disable the usage/management of supported packaging formats by adding their ids to the file /etc/bauh/gems.forbidden. This will prevent their management code to be loaded.
Example (one id per line):
~/.config/bauh (or /etc/bauh for root): stores configuration files
~/.cache/bauh (or /var/cache/bauh for root): stores data about your installed applications, databases, indexes, etc. Files are stored here to provide a faster initialization and data recovery.
/tmp/bauh@$USER (e.g: /tmp/bauh@root): stores logging and temporary files (e.g: build dependencies)
Custom themes can be provided by adding their files at ~/.local/share/bauh/themes (or /usr/share/bauh/themes for root). Sub-folders are allowed.
Themes are composed by 2 required and 1 optional files sharing the same name: my_theme.qss: file with the qss rules. Full example: light.qss my_theme.meta: file defining the theme's data. Full example: light.meta available fields: name: name that will be displayed on the interface. It supports translations by adding additional name fields with brackets and the language code (e.g: name[es]=Mi tema) description: theme's description that will be displayed on the interface. It supports translations like name (e.g: description[es] = Mi tema). version: theme's version. It just works as information at the moment. (e.g: 1.0) root_theme: optional attribute that points to a theme that must be loaded before the theme. It supports the bauh's default theme keys (e.g: default, light, ...) or a file path (e.g: /path/to/root/file.qss). abstract: optional boolean attribute (true/false) that should only be used by themes that are not complete on their own and just work as a base (root) for other themes. Abstract themes are not displayed on the interface. Full example: default.qss my_theme.vars: optional file defining key=value pairs of variables that will be available for the .qss file (can be referenced through the symbol @. e.g @my_var). Full example: light.vars common theme variables available: style_dir: path to the .qss file directory. Example: @style_dir/my_icon.svg images: path to bauh's icons directory (gem icons are not available through this variable). Example: @images/logo.svg
Icon paths defined in ~/.config/bauh/config.yml
Icons from the system with the following names: bauh_tray_default and bauh_tray_updates
Own packaged icons
For now it only allows checking for software updates (bauh-cli updates).
To verify the available commands: bauh-cli --help.
To list the command parameters: bauh-cli [command] --help. (e.g: bauh-cli updates --help)
Disable the application types you do not want to deal with
If you don't care about restarting the app every time a new supported package technology is installed, enable single_dependency_checking. This can reduce the application response time, since it won't need to recheck if the required technologies are available on your system every time a given action is executed.
If you don't mind to see the applications icons, you can disable them via download: icons: false. The application may have a slight response improvement, since it will reduce the IO and parallelism within it.
For a faster initialization process, consider raising the values of the settings properties associated with disk caching and the property boot.load_apps to false.
view: code associated with the graphical interface
gems: code responsible to work with the different packaging technologies (every submodule deals with one or more types)
api: code abstractions representing the main actions that a user can do with Linux packages (search, install, ...). These abstractions are implemented by the gems, and the view code is only attached to them (it does not know how the gems handle these actions)
commons: common code used by gems and view
Support for other packaging technologies
Separate modules for each packaging technology
Memory and performance improvements
Improve user experience
You can support this project through ko-fi.