cargo-deb

A cargo subcommand that generates Debian packages from information in Cargo.toml (by kornelski)

Cargo-deb Alternatives

Similar projects and alternatives to cargo-deb

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better cargo-deb alternative or higher similarity.

cargo-deb reviews and mentions

Posts with mentions or reviews of cargo-deb. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-04.
  • AMDGPU_TOP v0.1.2 - switch to crossterm-backend, add simple fdinfo viewer
    6 projects | /r/linux_gaming | 4 Apr 2023
    Ok, AMDGPU_TOP v0.1.3 is released. And the deb package is released at the same time (thanks cargo-deb).
  • How do I turn my shell into a package?
    2 projects | /r/rust | 27 Jun 2022
    cargo deb?
  • Rust for the Kernel Could Possibly Be Merged for Linux 5.20
    13 projects | news.ycombinator.com | 23 Jun 2022
    Rust actually works fine with distros. See for example https://github.com/kornelski/cargo-deb and https://wiki.archlinux.org/title/Rust_package_guidelines

    I use Arch Linux and Most Rust programs I use are installed from the Arch repositories or AUR. Rust packages are very well integrated with the distro, they depend on distro packages and have other packages depend on it. As far as the user is concerned, the Rust build system is just a developer-only stuff like CMake or autotools or ninja or whatever.

    Anyway I would like to point out that C++ also do something similar to what Rust libraries typically do, which is to use header-only libraries that don't appear as separate distro packages. It's as if every Rust library meant to be used by Rust programs (as opposed to libraries that expose a C API that can be called by other languages) were a header-only library. And this is actually great because Rust (like C++) monomorphizes generics, that is, if you call a generic function defined on another crate, the compiler actually generates a new function just with the type parameters you supplied, and there's no way the library can know upfront which generic instantiations will happen over all programs that use it.

    On the reproducibility front, I think it would be great if C program actually did what Rust does and pinned the exact damn versions of all libraries they use (like Cargo.toml does)

  • A note from our sponsor - SaaSHub
    www.saashub.com | 2 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic cargo-deb repo stats
3
371
7.8
8 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com