-
Notifications
You must be signed in to change notification settings - Fork 546
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
Activate Experimental Platforms #3805
Comments
Duplicate of #2763 |
To be clear, as explained in that issue, there are strong constraints related to the change, it isn't as easy as doing a mass Besides, it's a somewhat "breaking" change (dropping support for older versions of Julia), maintainers of the Julia packages using the jlls may not be happy about that. We have had a few maintainers that specifically didn't want to move to 1.6 only because they wanted to support previous versions of Julia for new versions of the package, so there is also that to keep in mind. In addition, I was already planning to make |
Ok, thanks. Then I'll keep on sending over PRs as I find dependencies in my stack that can be updated, but won't push anything more systemic. :)
|
There are currently 214 instances of
platforms = supported_platforms()
in the Yggdrasil code base, i.e. cases where (mainly because the script has yet to be updated), experimental platforms like Apple Silicon are not supported. A rough grep ofbuild_tarballs(ARGS
suggests this is ~25% (214 / 926) of binary files.This migration is a very specific change which is repetitive and creates (what I assume to be) an added burden on maintainers.
Would it make sense to get a few people together on a couple of afternoons and do an 'experimental platforms hackathon' to move this number from 25% towards ~0%? This could be planned so that it is maximally convenient for maintainers and so that open PRs don't pollute the repo.
Thoughts? @giordano
The text was updated successfully, but these errors were encountered: