cargo-dist
cargo-dist copied to clipboard
📦 shippable application packaging
Windows has a Better and Worse story for updating PATH: * Better: you can just modify `HKCU:\Environment\Path` and every windows shell should respect that * Worse: there is no equivalent...
install-path should support an option to install to "the proper place" on windows. Can't remember all the %options% and which ones are the Good Ones. This wouldn't make sense on...
Some terminals/clis have explicit support for tab-completion integration. Is that something cargo-dist can/should help with in some way? Generating it? Packaging it? Installing it? Out of scope for MVP I...
Is there already some discussion regarding supporting library building? I am talking about RPMs, DEBs, etc. I do have some opinions and might contribute.
It'd be nice if you could customize the format of the title of each generated Github release. Currently, it looks like it pulls the title from the changelog if available,...
I and a lot of NixOs users, use [rust-overlay](https://github.com/oxalica/rust-overlay)(or fenix) to manage the installed rust toolchain, selecting and installing targets and Rust versions in our flake.nix or similiar files. I...
We have two sample generic builds so far: [C](https://github.com/axodotdev/cargo-dist-c-example) and [JavaScript](https://github.com/axodotdev/axolotlsay-js). There's also a real-world [Objective C sample](https://github.com/mistydemeo/mt32-volume). We should consider what other languages we might want to demo too....
I think it would be nice to support creating `pkg` installers for macOS. Compared to `dmg`/`app` this could be more suitable for CLI applications (#24). For example, [starship](https://github.com/starship/starship/tree/master/install/macos_packages) publishes `pkg`...
I'm building a binary distributable that relies on a library crate, which itself dynamically links to SDL2. For windows builds, the build.rs of that library sticks the correct x86_64 or...
I use [Renovate](https://www.mend.io/renovate/) on my repositories which tends to look at the cargo-dist generated workflow, find that it's running builds on `ubuntu-20.04` and "helpfully" upgrades it to `ubuntu-22.04` which then...