CODEWITHSUNDEEP
haskelldependenciescabalhackage
jberryman
jberryman

Reputation: 16645

hackage showing incorrect dependencies for library package with executable sections

Hackage shows the union of the dependencies of the Library section as well as all Executable sections, even when I conditionally hide them behind a flag set to false.

I've only found this ancient, supposedly-fixed bug which claims that specifying cabal >= 1.18 solves things, but that doesn't seem to be the case.

What do I need to do to have hackage show only dependencies for the Library section, when the package includes Executable sections?

Here is the package that's giving me issues.

Upvotes: 1

Views: 64

Answers (1)

Joachim Breitner
Joachim Breitner

Reputation: 25782

This is not something you can control: If there is an executable section, hackage will expect that users will want to build them. This makes sense, and making that configurable will only cause unnecessary complications.

The proper fix in this case is to put the test suite and benchmark programs into proper Cabal sections of that type. See https://www.haskell.org/cabal/users-guide/developing-packages.html#test-suites and https://www.haskell.org/cabal/users-guide/developing-packages.html#benchmarks for their documentation.

Upvotes: 1

Related Questions