Fabrizio Ferrai

As Thomas noted, there's no real convention for YAML and it's about the surrounding conventions - PureScript uses CamelCase so that's likely to be the most natural choice. I'd say...

I think it's good to have something like this, but I'd like to have it under `spago init --subpackage PKG`. And we can likely start with a smaller amount of...

We won't need any new type, the `PackageConfig` supports everything we need - subpackages will only need their `withWorkspace` set to `Nothing`

The `publish` command is rebuilding your package using the Registry solver, which other users will use when interacting with your package. As you noted in the screenshot, the version bounds...

Ah, I misread the error in the screenshot - indeed everything else is correct, except that Spago is not installing the missing packages. We should be fetching them before issuing...

Probably? That would be the first thing I would try. Then I would [add a test](https://github.com/purescript/spago/blob/master/test/Spago/Publish.purs) and see how it goes. (tip for tests: use `itOnly` to only run a...

Yes, Spago carries a lot of local state through its Reader instance. I think it's fine to call it from other places as long as we pass the right flags...

These "env creation" functions are to be considered "expensive" (in term of running time), and are best run only at the beginning of the program, which is why they are...

It sounds like the tag declared in the `spago.yaml` does not match the git tag you're on

I think we can improve that error message.