Closed simonsan closed 1 year ago
And, indeed, it does circumvent it, in exactly the manner you described – cargo-install-update-config
to inspect, and -f
set features, per manual, or, indeed, edit the toml manually.
Woah, it's existing? :o
I didn't know that, sorry! Thanks for telling me! 👍🏽
Maybe it would make sense to mention this in just one line in the README? I also didn't know this and found it via issues.
Though I admit, I had only needed to look at the documentation, but I didn't because I didn't think there was any configuration at all.
Sure: 70ac01494200e2cb295cbe0e2ab1bbd068c73d48
Nice, thank you! Probably much more visible to newcomers like this!
I have a few binaries (e.g. arti (Tor) that need to be built with features enabled. In case of arti it's static building SQLite with a feature flag.
Not sure if this is an upstream issue, as I don't think
cargo install
is saving the features somewhere that were used when installing?cargo-update
could circumvent that if I could map it by myself in a, e.g.toml
file that is used for lookup when runningcargo install-update
.