-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question regarding MSYS2 conda repo #1484
Comments
Hi @ostueker, Thanks for the interest. We've not really documented the One thing to note is that here, You can see the recipes for all of them here: Because a meta-package is a normal package just without any content of its own beyond its dependencies there's no way to query which packages are and which are not meta-packages. Some of the packages are meta-packages in
.. but really, even here I should be using The script I mentioned at conda-forge/conda-forge.github.io#112 to convert packages from Because |
Sorry to bring this up. Some tutorials/posts suggest installing both m2w64-toolchain and mingw64. Is there any point in installing m2w64-toolchain if I already have mingw64 toolchain (through msys2 or mingw-w64 project)? |
@mingwandroid Are there any plans to resync with msys2 again? Specifically I'm curious about the potential of easily conda-installing a version of gcc that supports C++17. |
I came across the conda repo with msys2 and mingw64 packages[1] and two related GitHub issues [2,3] after @mingwandroid 's work was mentioned on the Software Carpentry list[4].
I am intrigued by the integration of msys2 packages into the conda repositories and eager to use them.
Is there any documentation on these packages, i.e. which of them are meta-packages that can serve as root of the dependency tree?
I found that packages posix and m2w64-toolchain seem to install a large subset (but not all) of the available packages.
[1] https://anaconda.org/msys2/repo
[2] conda-forge/conda-forge.github.io#112
[3] conda-forge/staged-recipes#364 (comment)
[4] http://lists.software-carpentry.org/pipermail/discuss/2016-December/004910.html
The text was updated successfully, but these errors were encountered: