Matthew Kenigsberg
Matthew Kenigsberg
I think we need to do https://github.com/flox/flox/pull/2316 first
We use `temp_env` in a few places. Are there cases that doesn't work for? https://github.com/flox/flox/blob/353d4213491bb55db716d62e8cf9bff26b7fcc2c/cli/flox/src/utils/openers.rs#L199
Using an `aarch64-linux` container as a builder on `aarch64-darwin` is pretty fast since it's the same architecture. That solves the Linux image on Darwin but yeah for building x86 we...
We need to do this after anything that modifies the manifest - edit, install, remove, upgrade, pull
> * combine warnings for `flox edit`, maybe https://github.com/flox/flox/pull/1967 ended up getting closed without merging
This is caused by the fact that we're using `export` to print env vars, and `export` uses `$'...'` when a var contains unicode: ``` $ export normal_var="normal_var" $ export fire="🔥"...
Still need to fix some of the unit tests
@edolstra could you take another look at this?
Do we have both a nightly channel and by-commit? It looks like we're probably setting `FLOX_SENTRY_ENV` to `nightly`for `by-commit` builds: ``` > curl https://downloads.flox.dev/by-env/nightly/LATEST_VERSION 1.1.0-28-g84a33517 ```
> There is no `by-commit` channel really. Each of `by-commit/` could be considered a channel, but since there is always going to be only one version in `by-commit/` there is...