Skip to content
New issue

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

Provide winget artifact in release #114

Open
paultyng opened this issue May 23, 2020 · 6 comments
Open

Provide winget artifact in release #114

paultyng opened this issue May 23, 2020 · 6 comments
Labels
ci Continuous integration/delivery related

Comments

@paultyng
Copy link
Contributor

Related to #55 and #47, this is the new Windows package manager from Microsoft.

@paultyng paultyng added the ci Continuous integration/delivery related label May 23, 2020
@radeksimko
Copy link
Member

I agree we should do it, but just to set the expectations, this won't replace Scoop or Chocolatey work, more importantly WinGet only supports alternative sources as the single point of truth for now:

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 retrieve 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.

So even if we did publish our own source/repo for WinGet it's unlikely anyone would use it. They would have to use it exclusively and loose access to the community source.

The only thing we could do is publish updates to the community repo, but given that it's PR-driven process it's not something we can easily automate and probably shouldn't anyway.

TL;DR We are waiting for Microsoft at this point.

@radeksimko
Copy link
Member

I can't find any more specific docs online, but it looks like additional 3rd-party sources are now supported for WinGet:
microsoft/winget-cli#226 (comment)

@denelon
Copy link

denelon commented May 19, 2021

Third party sources are supported by the Windows Package Manager client. We are working on the reference implementation of the REST API, and it will be released soon[tm].

@Sup3rlativ3
Copy link

Hello,

Is this still something being worked on? I'm automating some desktop images and I've found that tf isn't available.

@denelon
Copy link

denelon commented Nov 22, 2021

From the Windows Package Manager side, we still need to implement support for .zip:

A community driven draft specification is in progress:

We have also released the Windows Package Manager Manifest Creator to help publish manifests to the Windows Package Manager Community App Repository with CI/CD scenarios. For organizations wishing to host their own source repository, a reference implementation is available.

@HenrikStanley
Copy link

It seems like this functionality has now been added to winget, so it should now be possible to create a winget package based on .zip:

#114

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous integration/delivery related
Projects
None yet
Development

No branches or pull requests

5 participants