-
Notifications
You must be signed in to change notification settings - Fork 65
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI Reform with cargo decouple #226
Comments
Okay for next major we need a logical way to distinguish between geiger and cargo options Targeting major 0.12.0 release with all these breaking changes Please open an issue for any proposed / desired change and then refer back to this tracker :) I am proposing the below
This would mean that we remove --build-dependencies and --dev-dependencies And introducing different run types which have own separate report output mirroring cargo usage Essentially cargo geiger Question becomes where do we intro geiger options and best way to go by with it? Let's look at what we need to support for geiger opts We need the below geiger specific options #190 - -dX | --depth X (Proposed) Depth of dependencies (New in 0.12.0) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
This comment was made as part of 0.58.0 bump via 0.11.2 release
See 0.12.0 major changes from the next comment
See #244 for general discussion re: changes outside sub-issues - I've limited this issue to keep track of agreed changes
As part of working Cargo bump at #208
I came across the bit that builds the CompileOptions I have to adjust for cargo >= 0.58.0
0.52.0 CompileOptions - https://docs.rs/cargo/0.52.0/cargo/ops/struct.CompileOptions.html
0.58.0 CompileOptions - https://docs.rs/cargo/latest/cargo/ops/struct.CompileOptions.html
For the next minor release I would suggest we don't adjust any CLI options which are currently
Questions
Approach Proposed
Notes
--features <FEATURES>... Space or comma separated list of features to activate
The text was updated successfully, but these errors were encountered: