You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Linux dependencies described by the docs are defined independently of what the product's actual dependencies are. These should be guaranteed to be in sync such that if product dependencies are changed in any way, the docs will reflect that change. Today this is a manual process but it can be improved through the work being done in dotnet/core#5651.
Goal
Doc maintainers can use automation to validate and/or automatically update the docs such that the Linux packages described in the docs match up with the official product dependencies for each platform.
Just found this old issue. I'm not sure what to do with it... @mthalman Is there a specific ask? Use automation seems pretty generic since I don't really have an example of how to scan and get the dependencies or something?
This is more of an aspirational thing at this point. There doesn't yet exist a definitive list of dependencies that can be read programmatically. AFAIK, there aren't any plans to make such a thing available any time soon. So an automated approach to updating the docs isn't possible right now. I'm fine if you want to close this since it's not actionable at this time.
Summary
The Linux dependencies described by the docs are defined independently of what the product's actual dependencies are. These should be guaranteed to be in sync such that if product dependencies are changed in any way, the docs will reflect that change. Today this is a manual process but it can be improved through the work being done in dotnet/core#5651.
Goal
Doc maintainers can use automation to validate and/or automatically update the docs such that the Linux packages described in the docs match up with the official product dependencies for each platform.
Relevant content: https://docs.microsoft.com/dotnet/core/install/linux
cc @adegeo
The text was updated successfully, but these errors were encountered: