Matthew Kenigsberg

> Is it possible to create an initial manifest.yaml from a flake.nix? This will help migrate from using flake.nix to flox. Currently that's an entirely manual process. When we add...

nit: `.` is a flakeref, and `github:someuser/somerepo#tiny` is a flake output attribute. `install.foo` could also just be written as `.#foo` for consistency

Can you edit a `.flox/flake.nix` for a remote environment? An environment that's been pulled? (I guess maybe that's what pull --copy would be for?)

> * [ ] is this more than one issue? At least from an engineering perspective, I think it makes the most sense to do remote flakerefs first, and bundled...

I dislike the `[install.#tiny]` syntax lol

Just a heads up, this is going to have merge conflicts with https://github.com/flox/flox/pull/1299

> further breakdown: We also need upgrade

> * during lock: deny flakerefs to local paths, e.g. `..#` > could use runix flakeref parsers, or url with some heuristics (no scheme, [git+]file or path scheme) We can...

I think honestly it would be better to wait till 1299 gets in and then deal with conflicts :/

> * lock flake descriptors separately > ``` > nix flake metadata --json | jq '.url, .revision, .last_modified, .rev_count' > nix eval .#flox --apply 'drv: { > inherit (drv) version...