We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://packages.microsoft.com/
Since .NET 7, we officially support HTTP/3 (it's by default turned on). Our implementation of QUIC and HTTP/3 depends on https://github.com/microsoft/msquic. This dependency must be manually installed in Linux machines from packages.microsoft.com, see https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/quic/quic-overview#linux.
I suggest we specify this dependency (as optional) in the published dotnet runtime packages on packages.microsoft.com.
cc @rzikm @wfurt @CarnaViire @karelz
The text was updated successfully, but these errors were encountered:
is there such thing as optional dependency? Is there precedent you are aware of @ManickaP ?
Sorry, something went wrong.
https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends 'Suggests' would fit the bill. https://docs.fedoraproject.org/en-US/packaging-guidelines/WeakDependencies/#_weak_dependencies 'Weak' dependency, or even just a 'Hint'.
No branches or pull requests
URL(s)
https://packages.microsoft.com/
Description
Since .NET 7, we officially support HTTP/3 (it's by default turned on). Our implementation of QUIC and HTTP/3 depends on https://github.com/microsoft/msquic. This dependency must be manually installed in Linux machines from packages.microsoft.com, see https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/quic/quic-overview#linux.
I suggest we specify this dependency (as optional) in the published dotnet runtime packages on packages.microsoft.com.
cc @rzikm @wfurt @CarnaViire @karelz
The text was updated successfully, but these errors were encountered: