-
Notifications
You must be signed in to change notification settings - Fork 222
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
Package for winget (and maybe chocolatey?) #130
Comments
Dup of #23, pretty much. w64devkit isn't something that really needs updating often, nor are its updates ever anything critical or must have, and you can already obtain a compiler using mingw-w64 with winget. I'm not sure what the advantage would be. If you really prefer, you can write a script to update w64devkit instead of doing it manually. |
Peter0x44 precisely summarized my thoughts. This is itself a distribution,
and using a package manager to install a distribution is redundant. Though
I've made some tweaks, the toolchain here isn't anything special compared
to other Mingw-w64 distributions. The distribution mechanism, or lack
thereof, is the main feature.
|
I plan to make a winget package myself, if @skeeto doesn't mind. |
Sure, that's fine with me. If there's some way w64devkit could be tweaked
to accommodate such packaging, let me know. Such tweaks may be generally
helpful in other, similar use cases.
|
Just popping in to say that your (@skeeto) implementation of BusyBox-32 is much nicer than the one directly from Winget as it already has proper aliases made. Would absolutely love a Winget package. |
w64devkit is excellent software, but unfortunately it isn't yet packaged for any package manager. It could be worth the while to package it for winget, and perhaps also for chocolatey (since the former is only available for Windows 10 or higher. This way, w64devkit updates can be streamlined along with all others, instead of being a special case. Thanks!
The text was updated successfully, but these errors were encountered: