msys2
autossh
I can try, since I'm also interested, but will be my first package for MSYS2. If I am successful, I'll post here.
Timeframe: not for another 3 weeks. If I fail to report it is because I was not successful.
@pedro7 here is a PKGBUILD, untested but it does build https://github.com/equalsraf/MSYS2-packages/commit/99eca787163a6a69d5f6b728d8c7b96fb8446324
Question: do binutils and gcc belong to package base-devel?
Otherwise, a makedepends should be defined to include them (from binutils: strip)
Read our wikipage on building packages, especially this part:
The core packages groups you need to install if you wish to build from PKGBUILDs are:
base-develfor any buildingmsys2-develfor building msys2 packagesmingw-w64-i686-toolchainfor building mingw32 packagesmingw-w64-x86_64-toolchainfor building mingw64 packages
Also, the msys2-packages repository is supposed to stay minimal, only containing tools and programs necessary for building and then maybe some generally useful tools. We're not trying to make another Cygwin.
Can you make a case for why autossh should be included in MSYS2?
I thought you were trying to create a cygwin which would not depend on the external setup-x86_64.exe and would be as self-contained as possible.
We're not trying to make another Cygwin.
Therefore the answer is no. autossh does not belong in MSYS2.
We would of course like to see Cygwin adopt pacman and PKGBUILDs, and it's good that MSYS2 can showcase them, but that's not the goal. The focus is to provide a repository of native Windows (mingw-w64) software with all the benefits of real (not like Chocolatey) package management and an environment for building it with ease.
@transtone, would you like to comment, or did my explanation convince you as well?
Note that you're free to create your own PKGBUILD and/or binary repositories if that suits you. It's IMO super easy with the pacman suite.
We could create additional (officially unsupported) repository with software that users would like to see but it does collide with MSTS2 goals. Something between community and AUR in Arch.
I would just offer that autossh is a "generally useful tool" that helps with setting up build environments, for example ensuring an SSH tunnel into a build machine can be maintained in an open state despite irregularities in the internet connection. This would apply for example to an MSYS2 setup running on a home machine. I'd argue this is a key tool that helps developers to do their work.
