macports-ports VS winget-pkgs

I was curious if it was just some kind of horrific backlog but there didn't seem to be an oppressive number of PRs open, although it seems the new submissions drag their feet quite a bit https://github.com/macports/macports-ports/pulls?q=is%3Apr+i...

Also, it seems there is currently one in progress to drop the "6" qualifier on the ffmpeg binaries <https://github.com/macports/macports-ports/pull/23315/files> so it'll be fascinating to see if any new ffmpeg7 then subsequently puts the "7" back, beginning the cycle again

I don't understand how macports was able to build dmenu just fine but i can't. Here is macports's install script if it helps https://github.com/macports/macports-ports/tree/master/x11/dmenu

First, we must force our M1 Macs to emulate the terminal using the x86 architecture; I could not find any other way of compiling successfully, and for what I understand this problem is related to the fact that the ARM compiler is somewhat more strict than what one gets with x86 (source).

I know, I hear you. I'm so sorry for having you wait! I did work so hard to get it to work on MacPorts, and I'm actually in the process of merging all of my improvements to WebKitGTK+ to get it installable this way (https://github.com/macports/macports-ports/pull/11402). Additionally, there is a ton of work on a NixOS port of WebKitGTK+ (again using my work), so it should be reliably installable on macOS ASAP!

https://github.com/macports/macports-ports/blob/0c3c5e770185f4c3577b94a49170a961b88d1b98/editors/emacs/Portfile#L100-L141

For those who can't wait for homebrew, I've updated MacPorts https://github.com/macports/macports-ports/commit/4a4329dac1a3a1ea86fe1e3740d885c34f977e04.

> Godot - doesn't work

Godot has been working well for me under Rosetta (though just a small 2D project using GDScript). Godot 3.2.3 actually supports Apple Silicon[1] although there's no binary build just yet. I've recently submit a patch to MacPorts to enable native Apple Silicon[2] and have been using it since without any issues (so far).

[1]: https://docs.godotengine.org/en/stable/development/compiling...

[2]: https://github.com/macports/macports-ports/pull/9552

7.0 is now available: https://github.com/microsoft/winget-pkgs/pull/147886

I researched this for a WinGet thing: https://github.com/microsoft/winget-pkgs/pull/110618

Ah, reminds me of that time I requested a .editorconfig file in a Microsoft repo: https://github.com/microsoft/winget-pkgs/issues/329

Take dropbox as an example. This is what the yaml manifest looks like for that if you install it through winget. It literally has a hardcoded link to an .exe installer hosted by dropbox and then just set the flags to silent. I am not spreading misinformation, you are.

It's not quite the same though, as there are different considerations when using a repository of things a unified group has decided should be included and built (or slightly modified existing) packages for and a repo where anyone can submit a package that will go through some level of vetting. In the end I still believe most this discussion is really about individuals and how much trust they apply towards different groups and sources and is not really about Linux or Windows in particular as much.

1: https://github.com/microsoft/winget-pkgs

I never used winget, but probably: - https://github.com/microsoft/winget-pkgs/issues/107858 - https://github.com/Genymobile/scrcpy/issues/4027

It's probably not on the Store, winget pulls from both the Store and a community collection of manifests on GitHub: https://github.com/microsoft/winget-pkgs

I think that's part of the problem, if you don't have that package manager to bootstrap your signature key ring, DNS is your next best bootstrap. It is, of course, a terrible bootstrap for trust, but it is one so many users on Windows have been relying on for such a long time.

For power users on any modern Windows 10/Windows 11 there is at least WinGet now. Its manifests repo is becoming a very interesting (open) source of truth for common Windows applications. Admittedly, it in most cases doesn't seem to be checking specific code signatures in most cases either, but at least includes SHA checksums.

For instance, 7zip's manifests: https://github.com/microsoft/winget-pkgs/tree/master/manifes...

It's too bad there's still not a great option for "average user that doesn't know/trust how to use a CLI", given how sadly polluted the Microsoft Store can be for many common, especially Open Source, applications. For direct instance, because winget kindly includes Microsoft Store results when searching, there is a "7zip 22" in the Microsoft Store that costs some amount of money (winget details say "PaidUnknownPrice" for the pricing information; I'm on a corporate machine right now with the actual Store access locked so can't search in the actual Store right now) and the Publisher is listed as RepackagerExpress.com. (That website currently doesn't go anywhere, giving it a spot check.)

Having seen this, I may boot up my personal machine and try to report this specific Store listing for violating the Store's Open Source policies, though I'm unsure if such whackamole is all that useful. (Seems like it might be a useful winget feature request for it to provide Store Report URLs.)

For example, see that Firefox has /S here.