third-party repository support

[patrick330602]

Description of the new feature/enhancement

the current package managers for windows such as Scoop allows you to create your own repository, it would be awesome if you can add your own repo to allow users to customize the repo to their needs.

Proposed technical implementation details (optional)

[megamorf]

This is already possible as per https://github.com/microsoft/winget-cli#sources:

The client is built around the concept of sources; a set of packages effectively. Sources provide the ability to discover and retreive the metadata about the packages, so that the client can act on it.

The default source reflects that data available from the Community repo.

We plan to better support additional sources, and additional types of sources, in the future. For now, additional sources can be configured, but only one used at a time.

PS > winget source list
PS > winget source add --help

You can also simply throw some manifests on a fileshare and install them via:

PS > winget install --manifest \\fileserver\share\packagerepo\manifests\mycompany\myapp\1.0.0.yaml

See https://aka.ms/winget-command-source for details.

[megamorf]

Related issues:

• Support UNC source #160
• Be able to provide an own feed for offline usage #203
• Support internalized package repositories #213
• third-party repository support #226

[AntoineTurmel]

@megamorf but how do you make your own "source" server ?

[megamorf]

@AntoineTurmel As of right now the only available source type is Microsoft.PreIndexed.Package which is defined as:

winget-cli/src/AppInstallerRepositoryCore/Microsoft/PreIndexedPackageSourceFactory.h

Lines 11 to 18 in e997f3e

	// A source where the index is precomputed and stored on a server within an optional MSIX package.
	// In addition, the manifest files are also individually available on the server.
	// Arg :: Expected to be a fully qualified path to the root of the data.
	// This can be a web location such as https://somewhere/ or a local file share \\somewhere\
	// Under this path there must exist an MSIX package called "index.msix".
	// This must have a file called "index.db" contained within, which is a SQLiteIndex.
	// The index's paths refer to relative locations under the Arg value.
	// Data :: The package family name of the package at Arg + /index.msix.

Repo updates are done via Azure DevOps pipelines which don't seem to be included in the repos so no luck there. The only workaround for now is to have manifests and setups on a share and reference those paths in the manifest files. Then, as mentioned before, provide the --manifest during the winget install call.

[denelon]

#118 May be the most simple way to achieve third-party repository support.

[rbleattler]

This is already possible as per https://github.com/microsoft/winget-cli#sources:

The client is built around the concept of sources; a set of packages effectively. Sources provide the ability to discover and retreive the metadata about the packages, so that the client can act on it.
The default source reflects that data available from the Community repo.
We plan to better support additional sources, and additional types of sources, in the future. For now, additional sources can be configured, but only one used at a time.

PS > winget source list
PS > winget source add --help

You can also simply throw some manifests on a fileshare and install them via:

PS > winget install --manifest \\fileserver\share\packagerepo\manifests\mycompany\myapp\1.0.0.yaml

See https://aka.ms/winget-command-source for details.

This is already possible as per https://github.com/microsoft/winget-cli#sources:

The client is built around the concept of sources; a set of packages effectively. Sources provide the ability to discover and retreive the metadata about the packages, so that the client can act on it.
The default source reflects that data available from the Community repo.
We plan to better support additional sources, and additional types of sources, in the future. For now, additional sources can be configured, but only one used at a time.

PS > winget source list
PS > winget source add --help

You can also simply throw some manifests on a fileshare and install them via:

PS > winget install --manifest \\fileserver\share\packagerepo\manifests\mycompany\myapp\1.0.0.yaml

See https://aka.ms/winget-command-source for details.

Excellent contribution. Thank you for going out of your way to make this information available to those searching for some sort of solution.

[denelon]

It is possible to add additional repositories using winget source add.

For help you can execute winget source -?

Support for REST API based repositories is nearly complete in the client as of v0.3.

We will be providing a reference implementation of a REST API based source along with our v1.0 release.

[denelon]

Updating this issue to help users find the reference implementation at
https://github.com/microsoft/winget-cli-restsource

[mherrmann]

For people looking for a private repository, we offer this now at https://winget.pro. It's open source. You can either have us host it for you, or set it up on your own infrastructure.

[Croydon]

For people looking for a private repository, we offer this now as a hosted service at https://winget.pro.

Since this service isn't part of Microsoft, I don't think that you should use the winget name like that

[rbleattler]

I definitely agree with this…

For people looking for a private repository, we offer this now as a hosted service at https://winget.pro.

Since this service isn't part of Microsoft, I don't think that you should use the winget name like that

[thilojaeggi]

Not sure if it's ok to also advertise here but seeing since Winget.pro did it, I've created WinGetty over here: https://github.com/thilojaeggi/WinGetty which does everything Winget.pro does and more with the addition of it being open source and self-host able.