jgm/zip-archive

zip-archive not building with cabal-install's new-build

Closed this issue · 4 comments

dagit commented

It looks like there is a problem building zip-archive with cabal's new-build. See here: haskell/cabal#3394

jgm commented

I suspect it's a problem with cabal new-build rather than zip-archive.

+++ Jason Dagit [May 03 16 11:50 ]:

It looks like there is a problem building zip-archive with cabal's
new-build. See here: [1]haskell/cabal#3394

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or [2]view it on GitHub

References

  1. haskell/cabal#3394
  2. #28
dagit commented

I think there are actually two issues. One is the issue with new-build not reporting the error, but it looks like there is also a missing dependency for the custom setup.hs. See here: haskell/cabal#3394 (comment)

jgm commented

I had never heard of the custom-setup stanza in Cabal
files before, and I don't see anything about it in the
Cabal documentation

https://www.haskell.org/cabal/users-guide/developing-packages.html

Perhaps it is a new feature, but even if bleeding edge
cabal supported it, I wouldn't put it in the cabal file,
which needs to work with older setups too.

Note: this is presented as a "workaround" in the comment;
it is acknowledged to be a new-build bug, since you
shouldn't need to specify a base dependency for Setup.hs.

+++ Jason Dagit [May 03 16 16:18 ]:

I think there are actually two issues. One is the issue with new-build
not reporting the error, but it looks like there is also a missing
dependency for the custom setup.hs. See here: [1]haskell/cabal#3394
(comment)

—
You are receiving this because you commented.
Reply to this email directly or [2]view it on GitHub

References

  1. haskell/cabal#3394 (comment)
  2. #28 (comment)
lspitzner commented

Correct, the custom-setup stanza is a fresh addition in the just-released Cabal-1.24. It is not properly documented yet. I think the worst result of adding it would be a warning in older Cabals, but i would not risk it either; the workaround was meant as a local one, even when it means a bit of additional work for new-build zip-archive users.