-
Notifications
You must be signed in to change notification settings - Fork 9
Expand BuildEnv trait to include options, target and used components #567
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
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #567 +/- ##
==========================================
- Coverage 58.00% 57.97% -0.03%
==========================================
Files 216 217 +1
Lines 15945 15996 +51
==========================================
+ Hits 9249 9274 +25
- Misses 6696 6722 +26 ☔ View full report in Codecov by Sentry. |
f815bbf to
8d0f1b5
Compare
01623ae to
c1a5718
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one looks like it needs to be rebased past the ident reorg stuff too.
This allows the trait to replace a number of redundant arguments where solutions were already being passed which have access to the options from the solver as desired. Signed-off-by: Ryan Bottriell <rbottriell@ilm.com>
Build environments are not just package, but must also include information about what components of each package are being used, otherwise there's not enought information to reason about the complete environment state. Signed-off-by: Ryan Bottriell <ryan@bottriell.ca>
The target identifies the package and version being built that the build environment was resolved for. This is needed for some conditionals to be able to check if the condition is for the current package or one that actually should have been resolved in the build environment itself. Signed-off-by: Ryan Bottriell <ryan@bottriell.ca>
95a7c4f to
072505b
Compare
This allows the trait to replace redundant arguments where solutions were already being passed which have access to the options from the solver as desired. Also adds the
BuildEnvMembertrait, expanding it to report which components were used rather than just the packages that were resolved. Finally, adds atargetto each build env that identifies the package being built.There's no practical use for these extensions in this merge, but all are required in order to manage the conditional logic that is laid out for the v1 spec format.