Add design for dotnetup installation tracking#52834
Add design for dotnetup installation tracking#52834dsplaisted wants to merge 5 commits intodotnet:release/dnupfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a design document that describes how dotnetup will track installations, handle updates, and support uninstalls. The design is based on a discussion from the runtime installation design PR (#52409) and proposes using a shared manifest to track install specifications and installed components.
Changes:
- Added a new design document describing the installation tracking mechanism for dotnetup
- Defined the structure for install specs, installations, and subcomponents in the shared manifest
- Outlined the implementation approach for install, update, delete, and garbage collection operations
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
|
||
| ## Dotnetup shared manifest contents | ||
|
|
||
| ### Install specs |
There was a problem hiding this comment.
We should likely provide a json schema for the manifest file as well.
|
we should likely incorporate this comment in the spec #52792 (comment) |
nagilson
left a comment
nagilson
left a comment
There was a problem hiding this comment.
Please see my remaining feedback from now/last time - this has led to some great discussion!
nagilson
left a comment
nagilson
left a comment
There was a problem hiding this comment.
Thanks for incorporating my feedback, I think we can merge this!
| [ | ||
| { | ||
| "component": "sdk", | ||
| "versionOrChannel": "10", |
There was a problem hiding this comment.
specs will need to include a path to a global.json but we don't have to reflect this here.
|
This was included in #53290. |
Based on discussion we had on the runtime installation design, here's a proposal for how dotnetup should handle installation tracking, updates, and uninstalls.