cargo-dist
cargo-dist copied to clipboard
axodotdev
📦 shippable application packaging
Each installer is trying to do the minimal idiomatic thing for its "target audience", and that means a very inconsistent experience around "includes". Some of these are fundamental limitations, others...
I tried to integrate `cargo-dist` into my release workflow and hit a roadblock in form of my required rustflags. In my cargo config I set a rustflag to compile the...
Currently msi installers default to installing to `%PROGRAMFILES%\$app_name\`, but we have an install-path system that the shell installers already use. While I think the *default* is good, it would be...
I've tried out the new prerelease (`0.4.0-prerelease.2`), in a branch https://github.com/probe-rs/probe-rs/pull/1830. It seems that the package name gets truncated if it contains a dot. I've specified the libusb package like...
we make the checksums, let's use them in the installers to add a (thin) layer of security
e.g. https://github.com/libsql/sqld/blob/main/.github/workflows/publish.yml#L27
right now we have some stock output that happens when the installers are run. but often users like to print out branded messages, such as https://github.com/tursodatabase/turso-install/blob/main/install.sh#L31. it'd be cool to...
Currently we only support hardcoded support for github artifact download urls, which makes installers gated behind github. We can solve this by just letting the user specify. This should possibly...
Many authors of `CHANGELOG.md`/`RELEASES.md` files (including the maintainers of `cargo-dist` itself!) insert newlines in long paragraphs in order to wrap them at 80-ish columns. When GitHub renders such Markdown when...
