[Hackage] #860: Package seems to depend on itself

Hackage cvs-ghc at haskell.org
Tue Jul 5 15:13:19 CEST 2011

#860: Package seems to depend on itself
  Reporter:  guest              |        Owner:          
      Type:  defect             |       Status:  reopened
  Priority:  normal             |    Milestone:          
 Component:  hackageDB website  |      Version:          
  Severity:  normal             |   Resolution:          
  Keywords:                     |   Difficulty:  unknown 
Ghcversion:                     |     Platform:          
Changes (by igloo):

  * status:  closed => reopened
  * resolution:  invalid =>


 It's not a packaging bug; from `cabal/doc/developing-packages.markdown`:
 However having both a library and executables in a package does not work
 very well; if the executables depend on the library, they must
 explicitly list all the modules they directly or indirectly import from
 that library.  Fortunately, starting with Cabal, executables can
 also declare the package that they are in as a dependency, and Cabal
 will treat them as if they were in another package that dependended on
 the library.

 It would make sense for hackage to filter out the current package from the
 list of dependencies. (hmm, I wonder what happens with a version
 constraint that the package doesn't satisfy?).

Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/860#comment:2>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects

More information about the cabal-devel mailing list