The Cabal project's introduction of pkg:lib syntax for dependencies in cabal-version: 3.0 involved a misstep that was fixed in cabal-version: 3.4. See:
I suggest that future versions of Hpack should assume that if a user makes use of pkg:lib syntax, they intend to use at least cabal-version: 3.4 and not (as presently assumed) cabal-version: 3.0.
Not least, that is because Cabal-3.4.0.0, released 2021-02-06, is itself over 5 years old. That is, I doubt if anyone using Hpack today really wishes to pick cabal-version: 3.0 over cabal-version: 3.4.
The motivation is that I find myself adding verbatim: because Hpack is picking the 'broken' version of the syntax.
The Cabal project's introduction of
pkg:libsyntax for dependencies incabal-version: 3.0involved a misstep that was fixed incabal-version: 3.4. See:I suggest that future versions of Hpack should assume that if a user makes use of
pkg:libsyntax, they intend to use at leastcabal-version: 3.4and not (as presently assumed)cabal-version: 3.0.Not least, that is because
Cabal-3.4.0.0, released 2021-02-06, is itself over 5 years old. That is, I doubt if anyone using Hpack today really wishes to pickcabal-version: 3.0overcabal-version: 3.4.The motivation is that I find myself adding
verbatim:because Hpack is picking the 'broken' version of the syntax.