Fabrizio Ferrai

Yeah, I would like to support this. I am still of the opinion that idea3 has the better tradeoffs as it would work out of the box for everyone without...

> I also wonder if we could further specify the fuzzy matching idea to decrease the probability of duplicates like that happening These are good finds. I'm not sure though...

Exploring your idea of how this would work for core: I got the list of all the repos that might be purescript libraries (there are some spurious results, but bare...

There would be a fuzzy-matching part too - if the user would type `spago build -p semi`, we'd still build `semiring`, even if just typing `se` would have been enough....

I think having to deal with characters like `-` and `*` adds a bunch of complications, as the shell will want to expand the `*`, and we'd have to be...

> Another way we could address my concern about commands changing is adding a command for creating a new subpackage. When this is done, we could also check to see...

This works on bash, zsh and fish, but it requires manual installation. I don't know if we can do it with npm or nix, but I'm afraid it will have...

@deemp a few notes: - we'll need the `Spago.Generated.BuildInfo` import for the `spago --version` flag to work (see [the review of #980](https://github.com/purescript/spago/pull/980#pullrequestreview-1558640083)) - @thomashoneyman's `purescript-overlay` has a derivation for building...

@deemp are you still interested in this? I would like to have a flake in Spago itself, if it's possible to keep it simple

@deemp we can (and should) definitely support offline building (which is my preferred option) - but that means that we would need the build inputs (the `registry` and `registry-index` repo,...