Rust package guidelines

This document covers standards and guidelines on writing PKGBUILDs for software written in Rust.

Arch package guidelines

32-bitCLRCMakeCrossDKMSEclipseElectronFontFree PascalGNOMEGoHaskellJavaKDEKernelLispMesonMinGWNode.jsNonfreeOCamlPerlPHPPythonRRubyRustShellVCSWebWine

Package naming

When packaging Rust projects, the package name should almost always be the same as the name of the generated binary. Note that it does not make any sense to package library crates, so only crates with bins will be packaged. For ones that generate more than one binary, the upstream crate name is usually appropriate. In any event the package name should be entirely lowercase.


Most Rust projects may be built from tarballs, source archives (e.g. source links on GitHub releases), or any other published source. Alternatively many projects are published on which provides a stable download URL scheme for use with cargo. If desired, the PKGBUILD#source can use the following template:



While some Rust projects have external dependencies, most just use Rust ecosystem libraries that are statically embedded in the final binary. As such most projects will not need to specify many, if any, depends, only makedepends. The vast majority of Rust projects are designed to be built using the cargo dependency manager, which both orchestrates the download of libraries to satisfy build time dependencies as well as makes all the necessary calls to rustc, the actual Rust compiler. Currently both cargo and rustc are provided by the rust package, but there are also alternative ways of getting both of these together or separately including the rustup package. As such, the tool most PKGBUILDs are going to call is cargo and you should depend directly on it.


If a project requires the use of a nightly version of the Rust tool chain, use:



The rust dependency manager cargo is able to download all the libraries required to build a project ahead of time. Running this fetch in the prepare() stage enables the later build() and other stages to be run entirely offline.

prepare() {
    cargo fetch --locked --target "$CARCH-unknown-linux-gnu"


  • --locked tells cargo to strictly adhere to the versions specified in the Cargo.lock file and prevent it from updating dependencies. This is important for reproducible builds.
  • --target "$CARCH-unknown-linux-gnu" tells cargo to only fetch dependencies needed for the specific target platform being built, thus reducing downloads (see PKGBUILD#arch and Rust platform support).


Building a Rust package.

build() {
    export RUSTUP_TOOLCHAIN=stable
    export CARGO_TARGET_DIR=target
    cargo build --frozen --release --all-features


  • tells cargo to compile a release build (the default is a debug build)
  • tells cargo to stay offline and only use the versions specified in the Cargo.lock file and as cached by the fetch run in the prepare() stage. This is functionally equivalent to , which may also be used. This is important for reproducible builds.
  • --all-features tells cargo to compile with all features of the package enabled. Alternatively, use if you want enable only selected features.
  • RUSTUP_TOOLCHAIN=stable makes sure the default tool chain is set to stable in the event users have changed their default. Of course this should be set to nightly in the event that's what the upstream project requires. This avoids a common side effect of user preferences when not building in a chroot. Also note this is not required if the upstream project has a file or file in their sources that serves this purpose.
  • tells cargo to place the output in target relative to the current directory. This avoids a common side effect of user preferences when not building in a chroot.


Most Rust projects provide a simple way to run the test suite.

check() {
    export RUSTUP_TOOLCHAIN=stable
    cargo test --frozen --all-features

Avoid using the flag when running tests, otherwise the binary will be recompiled using the bench profile, replacing the one produced by build(). Alternatively, keep the flag and use a different value for CARGO_TARGET_DIR; however keep in mind that release mode also enables compiler optimizations and disables some features like integer overflow checks and macro, so in theory you could end up catching less problems. Both approaches will compile the dependencies again, slightly increasing total build time.


Rust builds binaries in and can simply be installed to .

package() {
    install -Dm0755 -t "$pkgdir/usr/bin/" "target/release/$pkgname"

If a package has more than one executable in you can use find command:

package() {
    find target/release \
        -maxdepth 1 \
        -executable \
        -type f \
        -exec install -Dm0755 -t "$pkgdir/usr/bin/" {} +

Notes about using cargo install

Some packages should install more files such as a man page or other assets. In the event that such a package does not have any other way to install these, one can use cargo install. In this case build() is unnecessary because cargo install forces rebuilding even if the package already has been built by using . The prepare() stage can still be used to fetch sources ahead of time:

package() {
    cd "$pkgname-$pkgver"
    export RUSTUP_TOOLCHAIN=stable 
    cargo install --no-track --frozen --all-features --root "$pkgdir/usr/" --path .

The argument should always be used, otherwise cargo install will create unwanted files such as or .

Example packages

Click Package Actions > Source Files in the package page to see its example PKGBUILD.

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.