msys2/MSYS2-packages-contrib?

[ghost]

You said you don't want to divert too much from Cygwin. But the needs for new packages can't be ignored. A lot of new packages are submitted as PRs. What about making a new repository for these packages? MSYS2 out of the box will not have the repository msys-contrib enabled. Users want to use it have to enable it manually via editing pacman config file.

[Biswa96]

You can create your own pacman repository and share it with others. It does not have to be in msys2.

[ghost]

@iahung2, do you have personal resources to maintain msys-contrib ? :)

No. This is the reason why I think something like msys-contrib should be under the umbrella of the MSYS2 project.

[sskras]

This would go against the original project aims:

[sskras]

It's a bit sad to see that the discussion was marked a resolved.

@iahung2, I very much support your aim and I would like to contribute to such 3rd party repo. :)
I just haven't developed the needed skills yet.

Although I have made some steps in researching experiments in that area:
https://disconnected.systems/blog/archlinux-repo-in-a-git-repo/
https://github.com/yujinakayama/pacman-repo
https://github.com/KSXGitHub/pacman-repo

There are even tutorials with *.github.io FQDNs in use:
https://www.sainnhe.dev/post/create-personal-arch-linux-package-repository/
https://www.arcolinuxiso.com/how-to-create-your-own-online-arch-linux-repository-on-github-and-use-it-on-any-arcolinux/

[ghost]

Neither you or me will have the ability to maintain such a repo in the long term.

[sskras]

Neither have the current contributors / maintainers, I think.
That's why it's important to gather an additional community. :P

[sskras]

But the needs for new packages can't be ignored. A lot of new packages are submitted as PRs.

Another option would be learning to use the Midipix project: https://midipix.org/#sec-midipix

... and research porting packages there, e,g.: https://dev.midipix.org/build/midipix_build/c/1d6d564?branch=main