Packaging is the process of creating, modifying and bundling the files your application needs to function outside your development environment. It may also include creating installers and/or artifacts for particular package managers or operating systems.
There are a couple of crates which let you package your application for desktop or server environment:
cargo-apk0.9.7 - Build
.apkfiles for Android.
cargo-arch0.1.5 - Arch Linux (PKGBUILD).
.appfor macOS and iOS,
.debfor Linux and
.msifor Windows (README says that Windows and macOS support is experimental). There are also plans for
.rpmsupport for Linux and
.apksupport for Android.
cargo-deb2.0.0-rc.2 - Build
.debpackages for Linux.
cargo-makepkg0.1.0 - Arch Linux (PKGBUILD). Might be abandoned.
cargo-pkgbuild0.1.1 - Arch Linux (PKGBUILD).
.rpm. Uses docker?
cargo-rpm0.8.0 - Build
.rpmpackages for Linux.
packapp0.4.0 - Formerly
cargo-app0.0.0 . Build
.appbundles for macOS.
There are some other crates which are somewhat orthogonal to the above crates, but are nevertheless useful for application distribution.
embed-resource2.3.0 - Inlcude Windows resources in your executables.
winres0.1.12 Include Windows resources in executables and DLLs.
self_update0.38.0 - In-place updates for Rust executables.
release-manager0.1.4 - Build your crate for multiple architectures and operating systems in one go. Might be abandoned.
cargo-tarball0.0.1 - Documentation seems sparse/non-existent. Presumably creates tarballs with your executables.
There are also some crates which target web technologies:
TODO: Look closer at the following crates: