Skip to content
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

Rules for MinGW on MacPorts #8

Open
AMDmi3 opened this issue Mar 20, 2018 · 1 comment
Open

Rules for MinGW on MacPorts #8

AMDmi3 opened this issue Mar 20, 2018 · 1 comment

Comments

@AMDmi3
Copy link
Member

AMDmi3 commented Mar 20, 2018

From repology/repology-updater#383 by @mojca:

The MinGW packages for MacPorts are split in a weird way. There's mingw-w64 which is some kind of a meta-package and is at the same version as *-w64-mingw32-crt, *-w64-mingw32-headers (and soon *-w64-mingw32-winpthreads).

Then *-w64-mingw32-gcc is basically gcc cross-compiler. And *-w64-mingw32-binutils is basically binutils for cross-compiler. I don't know against which packages these are supposed to be compared and I'm not sure how to write the rules for such a split, but it would be nice to correct this.

(Plus there's a bunch of abandonware i386-mingw32-*.)

@AMDmi3
Copy link
Member Author

AMDmi3 commented Mar 20, 2018

I'm a bit hesitant regarding these for now. At the one hand, they should be merged with corresponding gcc/binutils along with all cross-** packages. At the other hand, these are still useful as separate metapackages, otherwise the information on which repos have mingw support is hidden. We could both, but it's not possible to attach a package to multiple metapackages yet (see #163). I guess I'll leave this issue for later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant