-
Notifications
You must be signed in to change notification settings - Fork 552
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
List of packages yet to adopt artifacts #653
Comments
This list is not perfect, and includes
Also, some packages are more widely used than others. I have split the list into "must have" and "nice to have", but of course, I don't have a strong view on it. Happy to move things around further. |
Hi, Triangulate.jl is ready for it, but how to organize things to keep supporting Julia 1.0 ? Would also care about TetGen if time permits. |
Many packages have moved to 1.3+ so that they only support artifacts. I think in the spirit of moving forward, that is the right thing to do. |
@mlubin Is there an effort for moving the various solvers that JuMP users towards artifacts? |
The COIN solvers Cbc, Clp, and Ipopt have exceedingly complicated build systems (#509). I have no estimate for how much work is required to make it work. @juan-pablo-vielma managed to make the current binary builders work only after hours and hours of trial and error, and packaging everything up into one giant binary. Is this a "would be nice to use jll's" or will the current binary builder implementations stop working on a future 1.x release?!? GLPK is probably not too hard. I'll take a look. |
Let's continue the discussion about Clp in #509, no need to clutter this issue |
@ViralBShah The answer appears to be no, there isn't currently an effort. Is BinaryBuilder being deprecated? |
BinaryProvider, not BinaryBuilder: https://julialang.org/blog/2019/11/artifacts/ |
@StefanKarpinski Bringing this list to your notice. |
Could we try to semi automatically move some of these to Yggdrasil? E.g. look up the binarybuilder URL from the |
I've done that process manually in many cases. Given that there's only probably about 30 more such packages, perhaps not worth implementing tooling. |
Since MathOptInterface depends on JSONSchema, I would re-classify JSONSchema from "nice to have" to "must have". |
JSONSchema doesn't actually use BinaryProvider to for binaries. It is just used to download files in a test. @fredo-dedup isn't very active on Github, but I have commit access, and was in the process of tidying up the tests: fredo-dedup/JSONSchema.jl#13. I should remove the dependency on BinaryProvider while I'm at it. Edit: dependency removed in that PR. JSONSchema can be removed from the list above. |
Enough of the commonly used packages are done, that I feel we can close this issue. |
Updated that in the list above. |
NLOpt is also done |
Filed JuliaStrings/StringEncodings.jl#36 for StringEncodings.jl. Should be straighforward to update the package. |
I believe TextAnalysis and StringAnalysis both need libstemmer. |
Mongoc is done. |
The big missing one now is GR, which has a dependency on QT. |
GR is done now. |
This is based on a script @pfitzseb wrote. These are packages that do not use
jll
packages in 1.3+, but depend on BinaryProvider. This does not include packages that use their own binary download mechanisms.Must have group
Nice to have
The text was updated successfully, but these errors were encountered: