WinGet-based installation

[zkat]

It would be really great to be able to install bat on Windows through the windows package manager, winget.

[sharkdp]

Thank you very much for the feedback. Is there anything that we can do here or would it be best to open a ticket on the upstream issue tracker?

[zkat]

I think the main thing to do on your end is to set up a wix-based installer that can then be upstreamed.

[sharkdp]

We don't have any packaging-related code here in the repo (except for the automatic build of Debian packages). I also don't want to (and don't feel able to) maintain packages for systems that I don't personally use.

Is cargo-wix a requisite to have bat packaged in winget? Or just a convenient way to create winget packages?

[sharkdp]

I'm going to close this, as I don't really see any value in tracking this here. Let me know if someone thinks otherwise.

[sitiom]

@sharkdp The latest release of Winget now supports zip installation (https://github.com/microsoft/winget-cli/releases/tag/v1.4.10173). There is an ongoing PR for it:

• Sharkdp/bat/0.22.1 microsoft/winget-pkgs#95489

You only need to set up the Winget Releaser workflow when it is merged. Are you willing to accept a PR to add Winget Releaser in this repo (and possibly the other ones)?

[sharkdp]

Thank you. I really don't want to maintain any package management stuff inside this repository (except for what we have already with the Debian packages). Of course it would be great if bat could be installed via winget, but is a PUSH based approach really necessary? Can't winget package maintainers PULL the information from the bat repo? (just like everyone else)

[sharkdp]

If that's really the only way, I'm open to adding this workflow. Worst case, we can just delete it in case it creates problems and no one is here to fix them.

[sitiom]

Can't winget package maintainers PULL the information from the bat repo? (just like everyone else)

The problem is that only one maintainer is doing the pulling for most packages, and it is taking a toll on the CI (winget-pkgs-automation, same author as the Winget Releaser). Winget Releaser was created so that GitHub authors can take the pushing by themselves and help ease the CI for other packages on the automation.

Worst case, we can just delete it in case it creates problems and no one is here to fix them.

I can help as long as I use this software.

[sharkdp]

Ok. Let's do it.

[sitiom]

On the Winget Releaser side, vedantmgoyal9/winget-releaser#99 would have to be solved first.

[kritr-msft]

Seems like the issue is resolved! @sitiom are you planning on taking a stab at this ?

[sitiom]

As you can see, bat is not yet merged into Winget due to a blocking issue with dependencies (VCRedist), despite hyperfine and fd being merged, which have the same dependencies.

[sitiom]

PR now merged: microsoft/winget-pkgs#100636. Here is the Winget Releaser PR:

• Add Winget Releaser workflow #2519

[cprivitere]

Should probably add it to the readme as an install option. Worked for me today!

[sitiom]

Should probably add it to the readme as an install option. Worked for me today!

Already covered in the mentioned PR above. @sharkdp just has to review and merge it.