Paths module in package description or not?

Duncan Coutts duncan.coutts at
Mon Jun 1 18:45:35 EDT 2009

On Mon, 2009-05-25 at 10:40 +0200, Henning Thielemann wrote:
> Consider
> When I include Paths_mohws as Other-Modules, 'cabal haddock' aborts with:


> Which way is the intended one? Include Paths_mohws in package description 
> or not?

You should include it in the package description. The bug was fixed in
Cabal- (which is included with ghc-6.10.2).

> In general, shall automatically generated files appear in Cabal 
> file? I think they should not, since they are not part of the distribution 
> tarball. 

The source files are generated but the modules are part of the package.
If they were not mentioned in the package description then there would
be no way to say if they were exposed or not (though usually nobody
would want to expose the Paths module).

> So can I consider the linker error being a bug?

Well, only in the sense that it'd be nice if you got a better error
message at an earlier stage, like Cabal telling you that your package
description is incomplete because the package uses a module that's not
mentioned in the .cabal file.


More information about the cabal-devel mailing list