Elliot Saba

> Regardless, it is a bit "scary" that this uses packages without declaring a dependency. Alternatively, we could completely change this so that the hooks explicitly run with the environment...

Yes, but the expectation is that nobody is going to use anything other than `TOML`, `Artifacts` and `Libdl`, for example. If we wanted to restrict it to just those three,...

> Can we also document explicitly somewhere that people aren't allowed to e.g. mutate package source code inside a .pkg/ hook? Isn't this already enforced by setting package source to...

> I think you can still get around this, right? E.g. if you are root (a common situation for people that run their CI inside Docker containers where the USER...

Heh, we actually do have some powerpc releases available, but not for the latest release. :). You can check [the `versions.json`](https://julialang-s3.julialang.org/bin/versions.json) file for the gory details, which is what juliaup...

I don't think the `cli` piece adds much startup time. I would suggest you measure it before you try to re-implement it, it does a lot of stuff (and the...

Okay, had a talk with @vtjnash about this, and we're on board with trying this out. The concrete steps forward are: - [ ] Write the EA utility functions in...

On my linux machine, on a completely fresh depot, I can install it no problem: ``` $ mkdir -p /tmp.pkg_test && cd /tmp/pkg_test $ JULIA_DEPOT_PATH=. julia-1.6.3 -e 'import Pkg; Pkg.add("Zstd_jll")'...

So it turns out that this may not be a Pkg bug but rather a Julia problem. Pointing `julia-1.7` at a `release-1.7` checkout of Pkg, the issue does not appear,...

@ToucheSir, thanks for the detailed info, I think I found the error: https://github.com/FluxML/NNlib.jl/pull/367