Patch 1

[ket395]

JuliaLang/Pkg.jl@0333d55
Someone will need to add about 3 more tests once this set of fixes is completed to reduce maintenance burden.
And I'll censor myself about the backports issue because this is not my repo so different perspectives might be just suppressed.

note - I manually switched to my repo to ensure the non-contributors or Julia community can fairly access and assess the point I make.

Unexpected missing backport (assuming the BinaryBuilder.jl package does not currently work on 1.11)

For our sake. And for your own sake, please add a note somewhere or a post on Julia forum about why 1.10 has this fix but not it's successor, but then the succ of that has a fix. I'm assuming what anyone reading just this code and the communication without any opinions on Julia 1.x (adj. - extra) oneliner syntax will assume.

No I'm sorry, even if you teach Julia you won't immediately understand why Julia 1.11 breaks if it does, when using BB.jl with it. So like please be helpful.

[ket395]

Linking for your benefit.
JuliaLang/Pkg.jl#4151

Yes, I know the obvious. I have also known GR since a long time ago doesn't mean that implies everyone must know it to be correct about a totally different thing.

This Julia ecosystem bug has nothing to do with Juliaup.

[ket395]

The 5 million in your currency question

Why does BinaryBuilder get installed by Julia's package manager, which is a non trivial amount of waiting. When it's widely known since 2022 that it won't work on Julia 1.8 and above. Seems like manufactured inefficiency to me, and discourages me from contributing to the actual repo instead of the stupid suggestion auto generated by the Julia using x code path.

ERROR: InitError: BinaryBuilder supports only Julia v1.7.
Contribute to JuliaPackaging/JLLPrefixes.jl#6 (<https://github.com/JuliaPackaging/JLLPrefixes.jl/issues/6>)
if you care about supporting newer versions of Julia.

You don't get good contributors for free. You get sloppy ones. Or rather you have them.

PS - I forgot this. But I do hate that this had to be here, my bad.

PS - Ah! Silly me. I now clearly see not my fault that the Discussions tab is not open here as s expected. For a frictionless environment. Kind of like how people that prefer the terminal use tools like gh or glab instead of the websites as much as possible. It is a strongly unsympathetic decision for Github users in the flow state.

Manish, check out my kind of oldfangled, kinda newfangled, kinda cool, inevitably thought-provoking profile.

[ket395]

The link to ket395:patch-1 here is now defunct. Has been for some time. But my fork does exist.
Manish, check out my kind of oldfangled, kinda newfangled, kinda cool, inevitably thought-provoking profile.