Chocolatey works great, and working software matters way more than ideology to most users. You don't have to use it yourself, or trust it, or recommend it. Pretty much every package I've personally used within Chocolatey can be built with FOSS tools, does provide access to the source code, and the build recipes used to create the binary installers could be reproduced with enough effort. I don't have the time or desire to rebuild the world in a way that's entirely under my control though, I just need an easy way to get working versions of my dependencies installed.
It's a big messy world and not every single tool is always going to be open source or work properly entirely inside the confines of MSYS2. I can't use your 32 bit toolchain at all for example because I need SJLJ rather than dwarf EH. The CMake issue, IIRC, was an interaction with needing to use a non-MSYS2 i686-w64-mingw32 toolchain, not something I expected you to support. Switching to choco install cmake solved my issue immediately and was a faster way to move on to more important things.
I appreciate the desire to make Chocolatey unnecessary by improving MSYS2, and I can try to reproduce the issues again for proper bug reports. For now this solves a real problem, today, and I think it's awesome that Stefan put this together.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So... I don't share but respect your concerns and decided that it's better to delete the package from chocolatey.org. And learned that it's better to contact the authors before uploading packages for their software to chocolatey.org ;) But deleting is not that easy :) "Permanently deleting packages is not supported, but you can control how they are listed." You can only hide packages, even as their maintainer. So I contacted the moderators to really delete it... Let's see what happens ;) You can also "Report Abuse" on the package page if you like. That might accelerate things...
I uploaded the package to https://www.myget.org/gallery/zimmermann-choco/ for personal use and use at work. This is not connected to the Chocolatey community and the package won't get public attention or any "approval" there... But anyone who "trusts" me and reads this (and "knows what they are doing") may of course use it from there ;)
Hi Stefan, I'm not going to report it as abuse, if you guys feel so strongly that's it's worthwhile then I'll accept that and not kick up a(ny more) fuss, nor hold it against you. Please make pull requests for your features though as having Chocolatey's MSYS2 diverge from MSYS2 itself is not good.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I (and I'm guessing many others) need to interoperate with proprietary software and libraries built by non-GCC compilers "for various work related reasons." This is the main reason I can't use DW2 EH on 32 bit (I don't think it's supported by LLVM on Windows either, though this may have changed by now).
There are other similar-in-spirit native command-line installer wrappers for Windows, e.g. https://github.com/lukesampson/scoop that could also be used here. I agree on upstreaming and avoiding divergence.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi is it still possible to use this chocolatey package? I'm trying to automate a build on a clean VM and I've wasted a long time trying to figure out how to script the install.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The package is just not officially approved yet. I agreed with the Chocolatey moderators to first remove my extra features for CMD shell integration and provide them as a separate dependent msys2-cmd package, so that Chocolatey MSYS2 only installs pure MSYS2.
To install or update an unapproved package, you have to manually specify a version. For the latest release:
Chocolatey works great, and working software matters way more than ideology to most users. You don't have to use it yourself, or trust it, or recommend it. Pretty much every package I've personally used within Chocolatey can be built with FOSS tools, does provide access to the source code, and the build recipes used to create the binary installers could be reproduced with enough effort. I don't have the time or desire to rebuild the world in a way that's entirely under my control though, I just need an easy way to get working versions of my dependencies installed.
It's a big messy world and not every single tool is always going to be open source or work properly entirely inside the confines of MSYS2. I can't use your 32 bit toolchain at all for example because I need SJLJ rather than dwarf EH. The CMake issue, IIRC, was an interaction with needing to use a non-MSYS2 i686-w64-mingw32 toolchain, not something I expected you to support. Switching to
choco install cmake
solved my issue immediately and was a faster way to move on to more important things.I appreciate the desire to make Chocolatey unnecessary by improving MSYS2, and I can try to reproduce the issues again for proper bug reports. For now this solves a real problem, today, and I think it's awesome that Stefan put this together.
Tony, out of interest, why can't you use DW2 EH?
So... I don't share but respect your concerns and decided that it's better to delete the package from chocolatey.org. And learned that it's better to contact the authors before uploading packages for their software to chocolatey.org ;) But deleting is not that easy :) "Permanently deleting packages is not supported, but you can control how they are listed." You can only hide packages, even as their maintainer. So I contacted the moderators to really delete it... Let's see what happens ;) You can also "Report Abuse" on the package page if you like. That might accelerate things...
I uploaded the package to https://www.myget.org/gallery/zimmermann-choco/ for personal use and use at work. This is not connected to the Chocolatey community and the package won't get public attention or any "approval" there... But anyone who "trusts" me and reads this (and "knows what they are doing") may of course use it from there ;)
... or just use my choco-packages repo to create a custom package and put it wherever for personal use... but please not on chocolatey.org again!!! :)
I will try to contribute the extra CMD shell and further CMD/PowerShell stuff directly to MSYS2-packages.
Last edit: Stefan Zimmermann 2015-09-10
Hi Stefan, I'm not going to report it as abuse, if you guys feel so strongly that's it's worthwhile then I'll accept that and not kick up a(ny more) fuss, nor hold it against you. Please make pull requests for your features though as having Chocolatey's MSYS2 diverge from MSYS2 itself is not good.
I (and I'm guessing many others) need to interoperate with proprietary software and libraries built by non-GCC compilers "for various work related reasons." This is the main reason I can't use DW2 EH on 32 bit (I don't think it's supported by LLVM on Windows either, though this may have changed by now).
There are other similar-in-spirit native command-line installer wrappers for Windows, e.g. https://github.com/lukesampson/scoop that could also be used here. I agree on upstreaming and avoiding divergence.
Hi is it still possible to use this chocolatey package? I'm trying to automate a build on a clean VM and I've wasted a long time trying to figure out how to script the install.
Hi Paul. Yes. It is still possible: https://chocolatey.org/packages/msys2
The package is just not officially approved yet. I agreed with the Chocolatey moderators to first remove my extra features for CMD shell integration and provide them as a separate dependent msys2-cmd package, so that Chocolatey MSYS2 only installs pure MSYS2.
To install or update an unapproved package, you have to manually specify a version. For the latest release:
choco install msys2 -version 20150916.0.1
You can alternatively install and update the package from my Chocolatey feed at MyGet: https://www.myget.org/gallery/zimmermann-choco
choco install msys2 -source https://www.myget.org/F/zimmermann-choco/api/v2
If you are interested in the further development of the CMD shell integration features: https://github.com/userzimmermann/MSYS2-cmd
My proposed MSYS2-packages/filesystem-cmd will also fetch the scripts from the that repo in the future. Related issue and pull request:
https://github.com/Alexpux/MSYS2-packages/issues/344
https://github.com/Alexpux/MSYS2-packages/pull/350