Skip to content

Support public sublibraries #5256

Closed
Closed

Description

@expipiplus1

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.

Related: #4910, #2540 and #4564

I couldn't find an existing issue for this, and perhaps this is a better fit for the Stackage repo.

Activity

  1. expipiplus1 commented on Apr 11, 2020

    @expipiplus1
    ContributorAuthor
  2. Qiu233 commented on Jun 17, 2023

    @Qiu233

    Is there a way to declare multiple libraries in package.yaml?

  3. mpilgrem commented on Jun 17, 2023

    @mpilgrem
    Member

    @Qiu233, Cabal sublibraries? I think not, given: sol/hpack#483.

  4. hasufell commented on Jun 17, 2023

    @hasufell
    Contributor

    @mpilgrem hpack is an optional feature. One doesn't need to use it in order to use stack.

  5. changed the title [-]Support multiple public libraries[/-] [+]Support public sublibraries[/+] on Jun 17, 2023
  6. mpilgrem commented on Jun 17, 2023

    @mpilgrem
    Member

    On the topic of Stack supporting Cabal's public sublibraries, there is also #4745 (component-based builds).

  7. mmhat commented on Aug 15, 2023

    @mmhat

    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

    I think this issue can be closed, can't it?

  8. mpilgrem commented on Aug 15, 2023

    @mpilgrem
    Member

    @mmhat, if you are proposing this issue be closed because Stack supports public sublibraries, Stack does not (yet) support them.

  9. mpilgrem commented on Dec 1, 2023

    @mpilgrem
    Member

    I am closing this issue because #6343 has been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions