Linux packages

Besides the launcher and universal zip, Unvanquished distributions can also be found in some Linux package managers. These are not officially supported by the Unvanquished project.

Unvanquished update policy

The Unvanquished norm is that all players and server owners need to update at the same time when a new major version comes out (e.g. 0.54.x → 0.55.0). Differing major versions are incompatible. So when using one of the packages below, you should double-check that it is up to date with the official release distributed by the Unvanquished launcher or the Universal zip.

The current Unvanquished version is 0.56.2.

Getting ready for a release

You can subscribe to the Unvanquished release coordination topic on the forum. You can subscribe either with the Atom feed provided (can be done anonymously), or by mail by subscribing in the forum (requires a forum account).

This communication channel is the dedicated tool the Unvanquished team uses to announce upcoming releases and share other important information downstream distributors may want to know before hand.

Packages

The “Team” packages are maintained by Unvanquished developers, other packages are maintained by people outside the project and may not be verified.

Team	System	Package Name	Package Manager	Script	Maintainer
✅️	Flatpak	net.unvanquished.Unvanquished	Flathub	source	afontain, illwieckz
✅️	Arch Linux	unvanquished	AUR	source	Viech
✅️	NixOS	unvanquished	Nix	source	afontain
	Alt Linux	unvanquished	Sysiphus	source	shad

Packaging tips

• Due to the update policy, Unvanquished may not be suitable for package ecosystems such as Debian's where version stability is expected.
• You only have to rebuild the Dæmon engine (engine sources) for the system or distribution you target.
• Any .dpk file must be copied from the official release rather than built, because its hash must match when playing online.
• If you look at the universal zip, pkg/*.dpk plus the contents of the platform-specific zip, minus possibly crash_server, is the bare minimum for a usable install.
• All the .dpk files from a single release (the ones shipped in the universal zip) are required, even if some are listed with a same base name but different versions. This is because we use delta packages, with newer packages extending older ones. For example the Unvanquished 0.55.3 release required both res-weapons_0.55.3.dpk and res-weapons_0.55.dpk, the older one wasn't a leftover.
• Other nice-to-have bits are a desktop file, and server scripts from dist/.
• Supported architectures for Unvanquished are amd64 (x86-64), i686 (x86), armhf (32-bit ARM with hard float), and arm64.
• If downloads are discouraged/forbidden by the package system, you will need to bundle the NaCl runtime dependencies in the package.
• Excluding the NaCl runtime and Unvanquished gamelogic, you probably want to avoid using pre-built binaries. Pass -DUSE_EXTERNAL_DEPS_LIBS=OFF to CMake to avoid this.