Skip to content
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

Binaries #110

Closed
odow opened this issue Mar 27, 2024 · 0 comments · Fixed by #111
Closed

Binaries #110

odow opened this issue Mar 27, 2024 · 0 comments · Fixed by #111
Assignees

Comments

@odow
Copy link
Collaborator

odow commented Mar 27, 2024

I talked to Michael about the binaries hosted at https://pages.cs.wisc.edu/~ferris/path/julia/

We have the problem that if he updates these, then we're going to break users because these hashes will break:

libpath = Dict(
"windows" => (
"path50.dll",
"e227d19109f56628fccfdfedd7ecbdfd1667a3c975dd1d16a160a69d374d5474",
),
"macos" => (
"libpath50.dylib",
"8787de93d21f49a46146ebe2ef5844d1c20a80f934a85f60164f9ddc670412f8",
),
"silicon" => (
"libpath50.silicon.dylib",
"4e667615180565062013ab50a3968bbeddf3e510a9cdbfc27aa685152742b637",
),
"linux" => (
"libpath50.so",
"8c36baaea0952729788ec8d964253305b04b0289a1d74ca5606862c9ddb8f2fd",
),

The solution is for us to host the binaries, likely as release assets or in a different branch of this repo, and then use Artifacts.toml. That'll let us decide when to update the binaries, and we we can have control over the versioning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant