Matthew Kenigsberg
Matthew Kenigsberg
Discussed and we'll probably merge this once we're ready for it (may need to move the man page changes to the services folder), but we're not quite ready for it...
> * imperative option to enable impure? We need to record impure in the manifest so that subsequent builds of the environment when `--impure` isn't specified work
We don't want to make this "just work" by setting impure everywhere because that will make other flakes slower
> When attempting to use `env -i` as a "hashbang" in some existing build or test bash script, which actually is perhaps what would also be interesting for reproducible scripts,...
You must be running a different `env` than I am. But you need to pass `source` to `activate` for it to work in a shebang at the moment
Looks like all of this is done except adding runtime_dir to config, which I don't think we necessarily need. Thoughts on closing @ysndr?
For the wrong version, it looks like `try_find_compatible_yarn` resolves `nodejs` and `yarn` with two separate catalog requests. Because yarn builds in nodejs from whatever page it's on, we need to...
I believe this was closed by https://github.com/flox/flox/pull/2798
> That was only the yarn-berry part. The part ensuring that yarn and nodejs are resolved against the same page wasn’t done because of the offsite. I haven’t done much...
I'm not completely sure how common it is, but I believe package.json can specify both: https://github.com/flox/flox/blob/cc57091ff294e9ce5f6c52ce9113bac63d160beb/cli/flox/src/commands/init/node.rs#L251-L256