Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate all amazonka-* libraries into a single amazonka library #671

Open
brendanhay opened this issue Oct 10, 2021 · 9 comments
Open
Labels

Comments

@brendanhay
Copy link
Owner

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

See:

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
Copy link
Collaborator

endgame commented Oct 10, 2021

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

@ketzacoatl
Copy link

@endgame do you mean commercialhaskell/stack#5256?

@endgame
Copy link
Collaborator

endgame commented Oct 11, 2021

Yes, thanks.

@brendanhay
Copy link
Owner Author

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

@endgame
Copy link
Collaborator

endgame commented Oct 11, 2021

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
Copy link

istathar commented Nov 8, 2021

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
Copy link
Collaborator

endgame commented Nov 8, 2021

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
Copy link
Collaborator

endgame commented Dec 11, 2023

commercialhaskell/stack#6343 has been merged.

@michaelpj
Copy link

haskell.nix

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants