You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be super to be able to use cabal 3's visibility: public feature (https://fgaz.me/posts/2019-11-14-cabal-multiple-libraries/) on auxiliary libraries. Personally I'd like to make use of this feature to avoid cluttering the write-only namespace on Hackage/Stackage. This is also quite important IMO for backpack due to the number of different libraries required for a backpackized project.
Activity
expipiplus1 commentedon Apr 11, 2020
oh, perhaps stack already has support here, I see there's a test here: https://github.com/commercialhaskell/stack/tree/master/test/integration/tests/cabal-public-sublibraries
Qiu233 commentedon Jun 17, 2023
Is there a way to declare multiple libraries in
package.yaml?mpilgrem commentedon Jun 17, 2023
@Qiu233, Cabal sublibraries? I think not, given: sol/hpack#483.
hasufell commentedon Jun 17, 2023
@mpilgrem hpack is an optional feature. One doesn't need to use it in order to use stack.
[-]Support multiple public libraries[/-][+]Support public sublibraries[/+]mpilgrem commentedon Jun 17, 2023
On the topic of Stack supporting Cabal's public sublibraries, there is also #4745 (component-based builds).
mmhat commentedon Aug 15, 2023
I think this issue can be closed, can't it?
mpilgrem commentedon Aug 15, 2023
@mmhat, if you are proposing this issue be closed because Stack supports public sublibraries, Stack does not (yet) support them.
mpilgrem commentedon Dec 1, 2023
I am closing this issue because #6343 has been merged.