Feature request: add a .deb release
Hello,
Would you be open to packaging bacon for Debian as a .deb file? This would make it faster to install and update via something like deb-get. It would also open the door for things like shell completions. I haven't delved into it myself yet, but I think it can be done pretty easily using cargo-deb in a GitHub Action. If necessary, I can look into it and make a PR. Let me know what you think!
@nc7s I think you have an answer there.
https://tracker.debian.org/pkg/bacon
Unstable only yet.
Now it's in testing and, after the freeze, will be part of Debian 13/trixie.
Now it's in testing and, after the freeze, will be part of Debian 13/trixie.
It's in Debian now! I guess #347 can be closed.
Now it's in testing and, after the freeze, will be part of Debian 13/trixie.
It's in Debian now! I guess #347 can be closed.
No; my request is about adding a .deb to the GitHub releases. The Debian version will always lag behind.
No; my request is about adding a
.debto the GitHub releases. The Debian version will always lag behind.
My apologies; I just noticed myself that debian ships with bacon 3.12 as of writing, and not bacon 3.18. Also having it in Github releases would allow installation on ubuntu and all the others.
No; my request is about adding a
.debto the GitHub releases. The Debian version will always lag behind.My apologies; I just noticed myself that debian ships with bacon 3.12 as of writing, and not bacon 3.18. Also having it in Github releases would allow installation on ubuntu and all the others.
No worries; the FR was confusing. FWIW I think Ubuntu (will) work on a later release; but it's not on 24.04.
We'd have to make one deb file per architecture, right ?
We'd have to make one deb file per architecture, right ?
That's right. And the github task runner can at least build for the major architectures, x86 and a few different varieties of ARM.
In hindsight, this is a bit of a weird FR considering there's not even any binaries built. That is usually something you would do first. But both can be tackled at once.
The main reason I would like .deb files is for completions. The completions are not available by default when built from source (which is the only way to get the latest version currently).
However I just found out about https://github.com/Canop/bacon/blob/a4e1116d36aeb78697899d293d37aa9ca34a7946/CHANGELOG.md?plain=1#L52-L58 so it's a little less important. But still, .deb files can just do this by default, which is nicer.
(aside; why are the completions non-deterministic? This is very annoying)
$ bacon
clippy ex doc-open --version --no-summary --no-reverse --offline --send --all-features --project
nextest check-all check --prefs --wrap --help-line --init --job --export-locations --config-toml
run-long run doc --headless --no-wrap --no-help-line --listen --no-default-features --no-export-locations
test clippy-all --help --summary --reverse --list-jobs --no-listen --features --watch
$ bacon
ex clippy doc --version --no-summary --no-reverse --offline --send --all-features --project
doc-open check-all nextest --prefs --wrap --help-line --init --job --export-locations --config-toml
run clippy-all check --headless --no-wrap --no-help-line --listen --no-default-features --no-export-locations
run-long test --help --summary --reverse --list-jobs --no-listen --features --watch
why are the completions non-deterministic ?
This looks worth a dedicated issue