Request for personal-files interface for `msbuild-structured-log-viewer`

  • name: msbuild-structured-log-viewer
  • description: A logger for MSBuild that records a structured representation of executed targets, tasks, property and item values. It can greatly simplify build and provides a portable log interchange format (*.binlog) a rich interactive log viewer app.
  • snapcraft: dotnet-msbuild-structured-log-viewer-snap/snap/snapcraft.yaml at main · canonical/dotnet-msbuild-structured-log-viewer-snap · GitHub
  • upstream: GitHub - KirillOsenkov/MSBuildStructuredLog: A logger for MSBuild that records a structured representation of executed targets, tasks, property and item values.
  • upstream-relation: No direct relation. I work as a maintainer of the .NET toolchain in the Canonical Toolchains/Foundations team. I am creating a snap package for the MSBuild Structured Log Viewer as part of my work.
  • interfaces:
    • dot-nuget-packages:
      • request-type: installation
      • reasoning: .NET projects built outside the context of this snap, e.g, by a .NET SDK installed in the host, will cache their NuGet package files inside ~/.nuget/packages. This is the default location of the NuGet package cache. So, even if this snap overrides the cache location, these projects will still refer to the cache location they used when built. When this cache location is the default one, ~/.nuget/packages, the application errors out with an access denied message. So, to maintain interoperability with projects built outside the context of the log viewer, which is a common scenario, we need read/write access to the NuGet packages cache directory in the user’s home.
1 Like

This request has been added to the queue for review by the @reviewers team.

Hey @mateus-morais

The technical reasons are clear to me. Given that the directory does not clearly belong to the snap and you are not a member of the upstream project, I think limiting it to manual connection makes sense in this case.

If so, +1 from me for granting msbuild-structured-log-viewer access to ~/.nuget/packages via manually connected personal-files interface (#voteFor)

Thanks

Also +1 from me for manually connect to ~/.nuget/packages (#voteFor)

Voting period has ended. This request is approved with 2 votes for and 0 votes against.

This request was approved. The publisher is vetted. This is now live.

1 Like