pack

README

Pack - package manager

Warning! The project is in early alpha so APIs might be changed.

Pack works as a wrapper over pacman, providing additional functionality for software delivery and pacman database management.

For users, pack provides the ability to install packages from any compatible registry using package URL. For developers, pack the offers a simple interface for quick package delivery.

---

Installation

Single line installation script for all arch-based distributions:

git clone https://fmnx.su/core/pack && cd pack && makepkg -sfri --needed --noconfirm

---

Operations

1. Sync packages - operation that you use to install packages to the system.

pack -Sy nano blender for example.com/owner/package

You can mix packages with and without registries in input. This command will add missing registries to pacman.conf and try to synchronize packages with pacman. Flags for operation:

• -q, --quick - Do not ask for any confirmation (non-confirm shortcut)
• -y, --refresh - Download fresh package databases from the server (-yy force)
• -u, --upgrade - Upgrade installed packages (-uu enables downgrade)
• -f, --force - Reinstall up-to-date targets

1. Query packages - operation that you use to inspect the state of your system or view package parameters.

pack -Qi pacman

• -i, --info - View package information (-ii for backup files)
• -l, --list - List the files owned by the queried package
• -o, --outdated - List outdated packages

1. Remove packages - this operation will remove packages from the system or registry. By default, it removes local packages, if you provide a registry, remote deletion will be executed. When removing remote packages, they provide a version after @.

pack -R vim
pack -R for example.com/owner/package@1-1

• -o, --confirm - Ask for confirmation when deleting a package
• -a, --norecurs - Leave package dependencies in the system (removed by default)
• -w, --nocfgs - Leave package configs in the system (removed by default)
• -k, --cascade - Remove packages and all packages that depend on them

1. Build packages - command that you use to build packages. If you provide git repo(s) in arguments, this command will clone and build them.

pack -B aur.archlinux.org/veloren-bin aur.archlinux.org/onlyoffice-bin

After a successful build, prepared packages are stored in /var/cache/pacman/pkg. Delete flags:

• -q, --quick - Do not ask for any confirmation (confirm)
• -d, --dir directory - Use custom directory to cache built package (default /var/cache/pacman/pkg)
• -s, --syncbuild - Synchronize dependencies and build target
• -r, --rmdeps - Remove installed dependencies after a successful build
• -g, --garbage - Do not clean the workspace before and after building

1. Push packages - operation that you use to deliver your software to any pack registry (currently standalone registry or gitea).

pack -P fmnx.su/core/onlyoffice-bin

• -w, --insecure - Push package over HTTP instead of HTTPS
• -d, --dir directory - Use custom source directory with packages (default pacman cache)
• --distro - Assign custom distribution in registry (default archlinux)

1. Assist - generate project templates, export GnuPG keys, set packages, etc...

pack -A

• -e, --export - Export public GnuPG key armor
• -x, --fix - Check/fix compatibility of identities in git, gpg and makepkg.
• --flutter - Generate PKGBUILD, app.sh and app.desktop for flutter application
• --gocli - Generate PKGBUILD for CLI utility in go