depends on a non-library package

[kasbah]

I get this when doing a cabal install

cabal: InstallPlan: internal error: configured package depends on a non-library package

I believe the problem is the haddock dependency.

[wuzzeb]

Yes, haddock 2.15 was split into several packages but just changing the dependency to haddock-api was enough. There is also a build problem with optparse-applicative 0.10

http://hackage.haskell.org/package/optparse-applicative-0.10.0/changelog

Using haddock-api 2.15 and optparse-applicative 0.9.1.1 I was able to successfully build and run.

[kasbah]

I am getting these errors after modifying the dependencies. Not sure if related.

Building dash-haskell-1.0.0.0...
Preprocessing executable 'dash-haskell' for dash-haskell-1.0.0.0...
[15 of 16] Compiling Options          ( src/Options.hs, dist/build/dash-haskell/dash-haskell-tmp/Options.o )

src/Options.hs:38:5:
    Couldn't match expected type ‘Parser DbProvider’
                with actual type ‘Mod OptionFields DbProvider -> Parser DbProvider’
    Probable cause: ‘nullOption’ is applied to too few arguments
    In the second argument of ‘(<$>)’, namely
      ‘nullOption
         (eitherReader toProvider
          <>
            long "dbprovider"
            <>
              short 'p'
              <>
                metavar "<provider,args>"
                <>
                  value (CabalSandbox Nothing)
                  <> help "a ghc package db provider: cabal|ghc|dir")’
    In the first argument of ‘(<*>)’, namely
      ‘Options
       <$>
         nullOption
           (eitherReader toProvider
            <>
              long "dbprovider"
              <>
                short 'p'
                <>
                  metavar "<provider,args>"
                  <>
                    value (CabalSandbox Nothing)
                    <> help "a ghc package db provider: cabal|ghc|dir")’
...

Full log here.

[wuzzeb]

Yes, those are the errors from optparse-applicative 0.10, you need to use version 0.9 for now.

[jfeltz]

haddock-api 2.15 and lower bounded optparse 0.10 will go into the current milestone, thanks @wuzzeb, @kasbah, also I've patched safer bounds into master.