Accept multi-lib packages with public sublibraries

[brprice]

Now that cabal 3.8 has been released and multi-lib packages are no longer experimental, my understanding is that it is planned to update Hackage to accept multi-lib (with publicly visible sublibraries) packages (#852 (comment)).
I am opening this issue mostly to have something upstream to track the progress of this.

Some specific questions:

• Am I correct in thinking this is a planned feature?
• Any idea on an ETA?
• What (if anything) can I do to help progress this?
• Is this blocked by Post-multilibs checklist cabal#5660 (or anything else)?

Links to other tracking issues in the ecosystem:

• Consolidate all amazonka-* libraries into a single amazonka library brendanhay/amazonka#671
• Get ready for sublibraries. sol/hpack#483

[gbaz]

This is indeed a planned feature. I think the groundwork is basically laid except for porting hackage server to link against 3.8 and a new deploy. Once that's done, the UX might be a bit rough still, but it should all work at least (and we can improve the display as we go). Hopefully we can do this forward port and deploy in the next couple months, following the conclusion of gsoc projects which should also be incorporated into the upcoming deploy.

[cartazio]

I totally thought this was already done! Is my recollection incorrect or is some brave soul updating hackage code needed?

[gbaz]

I think it should work now, if anyone has a multilib package to upload.

[cartazio]

Ok cool! Are there any on hackage yet ? I’m curious what the ui looks like

[gbaz]

closing as done.

[michaelpj]

I'm also curious as to whether there are any examples in the wild. I think a number of us are keen to try this out but anxious not to mess up our packages accidentally, so it would be great to see an example which we could poke and check it seems to work okay!

[fgaz]

From a quick index grep, there is currently no such package on hackage

edit: but you can experiment by uploading candidates

[cartazio]

i may have 1-2 experiments lying around i can try in the near future once i clean them up

…

On Mon, May 15, 2023 at 8:46 AM Francesco Gazzetta ***@***.***> wrote: From a quick index grep, there is currently no such package on hackage — Reply to this email directly, view it on GitHub <#1119 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAABBQQWVLNVBZMBZGJGSN3XGIQSLANCNFSM56FFGKUQ> . You are receiving this because you commented.Message ID: ***@***.***>

[dhess]

I'm also curious as to whether there are any examples in the wild. I think a number of us are keen to try this out but anxious not to mess up our packages accidentally, so it would be great to see an example which we could poke and check it seems to work okay!

We will have one very shortly; no later than this year's Zurihac, I expect.

[georgefst]

How is one actually supposed to use this feature? I've run the usual cabal upload --publish $(cabal sdist | tail -n1), but I see no sign of anything other than the main library on Hackage. The others are present in the sdist tarball, and in fact were even before I set visibility: public for them, since they are depended on by the main lib. But none of their modules appear in the Hackage module list.

[fgaz]

Upload is allowed, but the hackage UI isn't there yet. You can still use the public libraries in other cabal packages though

[georgefst]

Upload is allowed, but the hackage UI isn't there yet.

Ah, yes, I now see that that's tracked in #1218.

You can still use the public libraries in other cabal packages though

Can confirm this does work! At least when adding to build-depends in a .cabal file (install --lib has issues: haskell/cabal#9074).