Hi, I have a package with one library and one executable. Something like this: name: ... version: ... library build-depends: base, array, containers, bytestring, random .... executable ... build-depends: base, array, containers, bytestring, filepath, directory, random, old-time, process, pretty Although I specified that the library depends only on few packages the installed package really depends on the union of packages for listed for the library and for the executable. I am using Cabal-1.2.3.0. Is this a known issue?
On Fri, 2008-05-30 at 08:51 +0200, Krasimir Angelov wrote:
Hi,
I have a package with one library and one executable. Something like this:
name: ... version: ...
library build-depends: base, array, containers, bytestring, random ....
executable ... build-depends: base, array, containers, bytestring, filepath, directory, random, old-time, process, pretty
Although I specified that the library depends only on few packages the installed package really depends on the union of packages for listed for the library and for the executable.
Yes.
I am using Cabal-1.2.3.0. Is this a known issue?
As far as I know that's exactly what it does. Can you be more specific about what the unexpected behaviour is? Are you saying that according to "ghc-pkg describe", the depends are just the build-depends from the library section and not the union? Duncan
participants (2)
-
Duncan Coutts -
Krasimir Angelov