Packages and modules
Malcolm.Wallace at cs.york.ac.uk
Fri Jul 7 05:07:02 EDT 2006
Simon Marlow <simonmarhaskell at gmail.com> wrote:
> > this is a finer granularity of dependency than Cabal is currently
> > good at expressing.
> By all means have package names scattered through the source code, but
> the dependencies still need to be specified in a single place for each
> project. The main reason is so that tools can grab the dependencies
> of a package without too much fuss: tools that turn Haskell packages
> into OS packages, for example.
Indeed. No problem with that. Any individual module might have a small
and specific set of package dependencies. The project as a whole will
have the union of all of those.
More information about the Libraries