Cabal developers meeting of the 26/10/2023

Thu Oct 26 17:56:15 UTC 2023

## Current Affairs (tickets and PRs of interests)

* Use response files for ghc invocations #9367:
https://github.com/haskell/cabal/pull/9367

* PackageInfo functionality is not guarded behind cabal-version. #9331 :
https://github.com/haskell/cabal/issues/9331
  * We have to be more careful in the future to guard new functionality
behind the cabal-version field of the file format.

* Terminology: Internal libraries are out, sublibraries are in! This is the
terminology that was already used in several blog posts, and as such we
must unify the vocabulary: https://github.com/haskell/cabal/pull/9371

* The exact-print parser topic has been raised from the dead once again,
and the situation is that many people seem to be interested in pursuing
experiments that cannot be realistically included in the cabal parsing
infrastructure. Due to the extreme sensitivity of the subject, a proposal
will have to go through the Technical Working Group before it's approved,
so that development can be smoother.

* lib:Cabal 3.10.2.1 has been released, with relaxed restrictions on the
contents of the c-sources stanza in the cabal file format.

## Summer of Code 2023

Suganya has landed the last PR to convert cabal errors to error codes.
Further documentation work is needed but the main goal has been reached.
Congratulations Suganya!

## Food for thought

Hécate: Bodigrim suggests that 3.10 could be kept on life support in order
to provide interfaces that we are trying to get rid of (namely v1-
commands, Custom setups, etc).
See original comment:
https://github.com/haskell/cabal/pull/9107#issuecomment-1773927473

*Conclusion: It's been decided that this would be too burdensome, and we
lack the resources to do such a thing.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/cabal-devel/attachments/20231026/9521f73c/attachment.html>