Elliot Saba

That did work in my testing, I figured that @KristofferC had a good reason for wanting to invalidate the world.

It's hard to tell; it looks to me like Weave just freezes.

The issue is that Pkg likes to set things to be read-only: https://github.com/JuliaLang/Pkg.jl/blob/6dd0e7c9e99d578aa5477e2c78c91a161ce4c357/src/Artifacts.jl#L79 I think the reason the areas of the ecosystem that I administer don't run into this is...

Because we identify artifacts by content-hash, it's a little risky to allow them to be made non-readonly, as we then break the implicit contract that this artifact can be shared...

I think the name of the setting should be something like `set_read_only = false`.

I guess it comes down to convenience. If you are okay with using something that just downloads to a scratch space and using that, that’s easiest for the Pkg devs.

So we’d have artifacts, lazy artifacts, and “utterly devoted to the sin of sloth” artifacts. :)

As far as a motivating reason for this, [BinaryBuilder2](https://github.com/JuliaPackaging/BinaryBuilder2.jl) will push up registry branches with stacks of new JLLs built and registered within it, [like this](https://github.com/staticfloat/General/tree/bb2/bb2). Eventually, I would like...

I think I recently addressed a similar question here: https://discourse.julialang.org/t/a-couple-of-questions-about-artifacts/33367/4 so I'm linking to that, as much of what I have to say is the same. First off, a few...

Ah, I didn’t realize that Package Compiler doesn’t ship the source code at all. Indeed, then the only two options are to create artifacts or to modify Package Compiler as...