-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Add some kind of install script to aid downstream packaging of emscripten #10169
Comments
You should implement the following items:
Currently the FreeBSD port is broken because it has no As another example, Arch linux port is broken for the same reason: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=emscripten-git Brokenness of ports is a result of you not providing configuration/installation/regression procedures. |
Open source rarely works by placing demands on other people's free time. As has been stated before, Emscripten core team maintains distribution/installation via emsdk and via direct clone from repository. If you would like to take the mantle of developing and maintaining Emscripten distributions to Linux distros you care about, or producing documentation to others for how they should do that, that would be great. You seem to know where to start the research already! |
I don't put demands, I am making a suggestion. |
I think there might have been a misunderstanding here. Just to clarify - thanks @yurivict for the suggestions. As @juj said, the main active devs here probably don't have time to look into it themselves, since we focus on emsdk packaging. But we'd be happy if someone did, and we'd like to help them. But it would require someone to take on the work. |
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant. |
This was fixed in #10761 |
Today packaging emscripten is kind of pain and not well supported. For example its not clear which files should be included in the package. See:
#10093
This should be done in cooperation with downstream package maintainers (or at least one so we know it works).
Current packages of emscripten can be found here: https://repology.org/project/emscripten/versions
The text was updated successfully, but these errors were encountered: