Carsten Csiky

In my PR i chose the 1. approach. I'm not publishing to google play atm, so luckily I don't need to care about googles rules. Ning already has a custom...

First idea to get the conversation started: Option | Default | Description -------- | --------- | -------------- no option | - | generates files in the target language and saves...

I would say either having the `--build` or the `--no-build` flag, but not both as that would be confusing. > I would vote for --build being the default (--no-build being...

No, I'm fine with that. That's probably what the user expects.

> Wonder if a command based CLI (like purs and spago) may make sense, otherwise there will end up being irrelevant combinations of options I was trying to avoid that...

Sure! Granted

Sure! Granted

I think I intended to license Ning under LGPL, but somehow that is not documented in the repo. Only here: https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/de.csicar.ning.yml I'll check what changes are necessary to make it...

Current proposal for how to deal with naming issues: https://github.com/purescript/registry#name-squatting-and-reassigning-names

If you're looking for a presentation tools for pdfs: [pdfpc](https://github.com/pdfpc/pdfpc) might be an option