Re: [xmonad] Did the latest patch break the build?

On Tue, May 28, 2013 at 6:48 PM, Carsten Mattner wrote:

On Tue, May 28, 2013 at 5:47 PM, Daniel Wagner wrote:

...

On 2013-05-28 11:34, Carsten Mattner wrote:

...

On Tue, May 28, 2013 at 5:09 PM, Daniel Wagner wrote:

...

On 2013-05-28 10:43, Carsten Mattner wrote:

...

Did the latest patch break the build for anyone else?

Building xmonad-contrib-0.11... ... XMonad/Util/CustomKeys.hs:66:29: Not in scope: `def'

It works for me with a fresh pull of xmonad and XMonadContrib. You'll need the latest xmonad from darcs, though.

I did delete ~/.ghc and ~/.cabal before rebuilding xmonad and XmonadContrib. Shouldn't XmonadContrib find and use the xmonad version just built from darcs HEAD? Do you know how it could believe there's no xmonad and it has to fetch+build from hackage?

It should, yes. If it doesn't, that's between you and your ghc-pkg, I guess. Maybe you built but did not register, or registered but in the wrong (local/global) database or something like that?

For whatever reason running cabal clean, cabal configure, cabal install in an xmonad darcs tree doesn't list xmonad in ghc-pkg list. Rerunning cabal instal in xmonad says it's a reinstall. What could be the reason?

The issue was all my fault. The xmonad-core tree had a cabal 1.17 sandbox from an experiment I forgot to remove and so cabal install installed it in the sandbox.