Support UNC source

As an enterprise IT administrator I want to be able to have a UNC source so I don't have to stand up APIs or web services to provide a private repository to my users.

This may mean that the repository is simply a "manifests" folder, and the client needs to traverse the structure to pull in the information in order to support the "search" command.

There should also be a corresponding PowerShell module to support UNC source manifest repositories. For example, Publish-Package, Get-Package, etc., similar to PowerShellGet.

Related issues:

Any news on this? UNC paths are needed to gain adoption in enterprise environments.

We've had an ask for:

Easier private sources winget-cli-restsource#135

We're also working on:

Develop Intune integration #215

There are currently (as of June 2022) many other features ranked higher than this one.

Squashed 'src/Valijson/valijson/' changes from 2dfc7499..94d3bfd3

Squashed 'src/Valijson/valijson/' changes from 2dfc7499..0b4771e2

Any update when this might be available?

Navigation Menu

Repository navigation

Support UNC source #160

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Support UNC source #160

Description

Activity

DrDallas commented on May 20, 2020

megamorf commented on May 23, 2020

ThatGuy48317 commented on Jun 27, 2022

denelon commented on Jun 27, 2022

fin-major commented on Aug 23, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions