I successfully created an archive tarball using the help from this website. I thought the documentation was not as clear as this blog.
I do have a problem though. I thought I could create a gitlab repo, and inside that gitlab repo put the tar ball and then give the url for the Artifacts.toml as that single file’s url without having to clone the entire repo, etc.
But when I test it with “download_artifact”, this seems to create a new sha256 hash every time so perhaps gitlab does not work this way.
Any ideas on what I’m doing wrong or what I should be doing?
The module Pkg.Artifacts has a rather low-level API. ArtifactUtils.jl is much more user-friendly.
1 Like
That looks interesting. It looks like a manual call though, is there a way to automated it with the package’s Artifacts.toml so that things get installed lazily for the user of the package? I’m just now downloading the package… I probably should have tried it out first before adding this follow up.
I think I know what the problem is after looking at your script. When I just do the “download” by itself, I get a webpage back asking for gitlab verification. Even though the package manager knows how to normally access gitlab for internal packages, it seems to be having a problem. I’ll see if I can figure out that part. I’m getting a gitlab webpage back from the download instead of the tarball.
Is that a private page which requires authentication? If so, I’m afraid artifacts can’t handle that at the moment. Depending on what you need exactly, there may be alternatives. If I remember correctly DataDeps.jl supports authentication to fetch files.