Auto-connection request for dotnet-runtime content interfaces

store-requests privileged-interfaces
1
  • names:
    • dotnet-runtime-60
    • dotnet-runtime-70
    • dotnet-runtime-80
    • dotnet-runtime-90
  • description: These are content snaps that provide the binaries of the .NET Runtime in its various major versions.
  • snapcraft:
  • upstream: GitHub - dotnet/dotnet: Home of .NET's Virtual Monolithic Repository which includes all the code needed to build the .NET SDK.
  • upstream-relation: I’m part of the Toolchains team at Canonical, which maintains both the .NET Runtime/SDK packages in Ubuntu, as well as their content snaps.
  • interfaces:
    • dotnet-runtime:
      • request-type: auto-connection
      • reasoning: Apps that depend on the .NET Runtime to run can use these content snaps as providers of the runtime. The goal with the runtime content interface to auto-connect is to make the snap experience more seamless for .NET applications by removing the need for non-technical users to snap connect after installing applications. All of the listed content snaps provide this interface.
2

It looks reasonable to me. +1 from me for granting requested global-auto connection (after publisher vetting)

3

+1 from me as well.

+2 votes for, 0 votes against, granting global content auto-connect to snaps:

  • dotnet-runtime-60
  • dotnet-runtime-70
  • dotnet-runtime-80
  • dotnet-runtime-90

I have vetted the publisher. This is now live.

1 Like