Consolidate all amazonka-* libraries into a single amazonka library

[brendanhay]

This is a tracking issue for Cabal's (and Hackage's) "Multiple public libraries" feature.

See:

• Announcement: https://fgaz.me/posts/2019-11-14-cabal-multiple-libraries/
• Original PR: [GSoC2018] Add support for multiple public libraries in a single package haskell/cabal#5526
• Cabal tracking issue: Post-multilibs checklist haskell/cabal#5660
• Hackage support (supposed): Update hackage-server for Cabal 3 haskell/hackage-server#852

There are currently 140~ services configured and roughly that number still unconfigured (ie. not generated) that I've held off generating in the hope the feature would eventually be available/usable. Since it doesn't appear like it's there yet, I'd like to have a more concrete estimate of when (if ever) the feature will be usable on Hackage, otherwise generating the services into separate packages should resume.

Please link and discuss any additional updates and relevant issues.

[endgame]

Stack support is another consideration: https://github.com/commercialhaskell/stack/issues/52561

[ketzacoatl]

@endgame do you mean commercialhaskell/stack#5256?

[endgame]

Yes, thanks.

[brendanhay]

This blog post may (or may not) be an indication of how likely such features will be supported by stack.

[endgame]

Yeah. That's pretty recent so can probably be taken as true. If we move to multiple public libraries in a single package (if/when Hackage supports that), we may create more interest in stack gaining that support, or we may end up locking amazonka out of the stack universe for a long time.

Also note: the nix world is downstream from the stackage world - most of their stuff is built on stackage snapshots. If you want to do this, we should probably liase with them first. I have no idea if cabal2nix etc support multiple public libraries, and we may inflict a great deal of pain.

[istathar]

I happen to know Stack is getting some additional maintainers shortly, which is great news. Michael came across a tad pessimistically in that post, but do I gather things like the multiple public libraries idea have caused a lot of pain.

[endgame]

That's good news. Still need to check where hackage is at with all this stuff, as well as cabal2nix and haskell.nix. No point getting a whizz-bang new version of Amazonka out the door if nobody can use it =(

[endgame]

commercialhaskell/stack#6343 has been merged.

[michaelpj]

haskell.nix

Just to say: haskell.nix works fine with multiple public libraries.