-
Notifications
You must be signed in to change notification settings - Fork 132
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
.NET 8: Tracking issue for repos specifying and regularly updating their dependencies. #2980
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
@MichaelSimons is this assertion correct?
|
To avoid confusion, it is really for any dependencies produced in source-build. Because there a cycles in the graph, a dependency could be built after. In that case, the dependency gets satisfied by previous source-built artifacts. Even if that is the case, we are building with a recent version and we would like to avoid pinned references in those cases. |
We do need to avoid product dependency cycles in order to not break the current official build and staging process. We can have cycles for toolset dependencies, but not for product dependencies. Do you have an example of one of these that exists today that we can analyze a bit? |
@MichaelSimons I believe I have all the child issues opened for this work |
Yep, that and the prebuilt detection work. |
Description
This is a repo tracking issue related to #2979. Repositories should:
eng/Version.Details.xml
files. They need only specify dependencies for repos that are produced earlier in source build.They should then either:
Repositories
The text was updated successfully, but these errors were encountered: