ffaf1 comments

Results 160 comments of


                                            ffaf1

'cabal check' or 'cabal sdist' ought to warn about non-ASCII characters

I will leave the decision to Hackage admins. It not as trivial as “UTF-8”, see [RFC 9839](https://www.rfc-editor.org/rfc/rfc9839.html), plus I guess OS oddities.

Updates to the cabal files created by cabal init

I agree with most suggestions. But most importantly I _strongly_ agree with a UX revamp for `cabal init`. As now the user has to enter input _fourteen times_ to finally...

Warning: [no-default-language] doesn't provide enough information

We don't have yet source positions, but pointing to the file and component should be doable.

Don't warn on `mhs-options` (fixes #11341)

Gershom (on Matrix) confirms that this should not impact Hackage. He points to x-fields as an option, but I understand this might not palatable to MicroHs developers.

[meta] Should for-ghc-only releases take up major release numbers?

What if we were to attach a `cabal-install` pre-release? Or is that out of the question?

`cabal check` complains about a missing `Setup.hs` script when using `build-type: Hooks`

This is not good, as Hackage will eventually use what `Cabal` say.

Allow 'if' for data-files section

What is `cabal sdist` supposed to do? Pack all of those files or conditionally exclude some?

Recognise SetupHooks.hs

Does this need backport? I think so, since it influences Hackage behaviour.

Recognise SetupHooks.hs

@mergify backport 3.16

Detect cycle in modules

Got bitten by this one too, would be nice to see this merged. @ndmitchell do you need a helping hand in low-level maintainership tasks (triaging issues, merging non-controversial patches, etc.)?