Closed NobodyXu closed 1 year ago
Recently upon running cargo binstall cargo-udeps
- the command cargo +nightly udeps
fails due to the expected libssl.so.1.1 version being outdated. Had to cargo install cargo-udeps --force
after to fix.
Recently upon running
cargo binstall cargo-udeps
- the commandcargo +nightly udeps
fails due to the expected libssl.so.1.1 version being outdated. Had tocargo install cargo-udeps --force
after to fix.
@Ktoks I've opened a new issue for this #648
Thank you.
Should also consider using https://github.com/kinnison/git-testament
@passcod Maybe we can introduce a --verbose
/-v
flag that when specified with -V
, caused the commit and more information to be printed?
Yeah I've made bosion for this for watchexec, but it's currently a little dependency heavy...
Yeah I've made bosion for this for watchexec, but it's currently a little dependency heavy...
Oh well, having to pull in gix
is indeed way too heavy.
Can we make gix
an optional feature and fallback to running external cmd git
if gix
is not enabled?
I'd rather figure out a different way to read the git info in pure rust, if possible, though a fallback wouldn't go amiss.
This is currently blocked on https://github.com/watchexec/watchexec/pull/615 since bosion currently uses old gix
version while cargo-binstall
uses gix 0.47
I've submit https://github.com/watchexec/watchexec/pull/619 for updating gix to v0.47
I just realized that if we run cargo-install
, then bosion
will fail to find a git repository.
vergen
supports several features to select git impl from git cli, git2 and gix and can disable git
.
We can check .git
in our build script and run git --version
to decide whether to disable git .
While binstall already uses gitoxide
, we still can't reuse that in build-dep due to different profiles used.
In profile.release
, we set abort-on-panic, which cannot be enabled in build-dep.
cargo-auditable
support right? looks like that PR closed the wrong issue?1182 did not implemented
cargo-auditable
support right? looks like that PR closed the wrong issue?
Well it's actually implemented much earlier than that (before v1.0.0) and this issue is now used to track for verbose version.
ah! cool thx
Use
cargo-auditable
to build the final release artifacts so that it contains all the dependencies used and is auditable.Related:
https://github.com/cross-rs/cross/issues/1172 https://github.com/rust-secure-code/cargo-auditable/issues/95