build(ci): try 1.12 with (almost) full stdlib collection in system image - #60139
build(ci): try 1.12 with (almost) full stdlib collection in system image#60139pankgeorg wants to merge 5 commits into
Conversation
Because it's not a stdlib in 1.12 |
The "stdlib" is a concept that eludes me 😅. Does it mean it's not in the default system image? Or that it's not the "default" way to do encryption any more? Part of the what this PR tries to "prove" as a concept, is that "default system image", "standard libraries" and even "default environment variables" are not "one size fits all" as they can lead to highly diverse experiences and thus I'm trying to collect the data to propose that they should be highly configurable, easily. Which, as a goal, may be beyond julia itself (and into juliaup or even unchartered territory). Let's see what the data will show, I'm still at hypothesis stage🤞🏾 |
It means it doesn't exist at all. |
3d0fa95 to
82800a1
Compare
|
I pushed a commit with a version of Pkg that includes JuliaLang/Pkg.jl#4518 so it can be included in the sysimage. I will see if I can understand why the REPL hangs. |
|
looks like this was only opened to trigger CI; closing to tidy up the tracker |
Experiment to benchmark
1.12.2-max(=julia 1.12.2 with 1.10 system image) startup times.Details
When adding Pkg there, I get
When adding MbedTLS, I get an issue about it not being found. I think it's fine.
Difference in size is ~300MB for the
usr/lib/juliafolder. I'd say that's negligible for the everyday user.