Matthew Kenigsberg

I tried with `--eval-cache` as well and that didn't seem to make a difference for `nix eval`. @tomberek am I holding it wrong? Or does `nix eval` actually not use...

For now let's comment out `go get`, `pip install`, `npm i` etc. We'll change if @jennymahmoudi changes her mind

@limeytexan this is similar to https://github.com/flox/flox/issues/1246 and relates to https://github.com/flox/flox/issues/1268, and my understanding from that ticket is that we should only set development env vars for a single package group...

Still needs a test

> How should we approach unit tests? I would add a bunch of tests for `new_documented`, and I would lean towards checking assertions about `RawManifest::to_string` rather than `RawManifest` itself, because...

The newline broke some tests

Needs one last change after changes serverside

Passing functional tests run at https://github.com/flox/flox/actions/runs/9038043980/job/24838364578

It doesn't mean we can't recover dangling symlinks, but just noting that we just discovered a possible way to end up in this situation is by running `brew upgrade --cask`,...

I would also suggest we link directly to the relevant instructions for macOS. Currently that would be https://flox.dev/docs/install-flox/#__tabbed_1_3, so I think we should change that from __tabbed_1_3 -> macos and...