Please consider joining stackage
Closed this issue · 12 comments
Hi,
I’m wondering whether to build a project of mine on top of unbound, but especially with academic software, the current maintenance status is unclear. The last upload was a year ago, which is already a lot on hackage.
If unbound were added to stackage, this would give me greater confidence that it is a maintained bit software, as at least build failures and test suite failures will be detected in a timely manner by the stackage guys. So in a way, it is free QA for your!
It is easy to join stackage and does not require you to use stackage or the stack tool: http://www.stackage.org/authors
Greetings,
Joachim
This is super old, but sometime when you get a chance, can you help me do this?
I’ll take care of it, by creating commercialhaskell/stackage#1794.
Thanks! Do I need to add anything to RepLib/Unbound? Let me know.
On Aug 19, 2016, at 10:29 AM, Joachim Breitner notifications@github.com wrote:
I’ll take care of it, by creating commercialhaskell/stackage#1794 commercialhaskell/stackage#1794.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #30 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ACAZdtpmdTmF-oPIL-Lk7aAYaMhb4eIZks5qhb3MgaJpZM4FzSyz.
Do I need to add anything to RepLib/Unbound? Let me know.
I think uploading the current state of the repository, including RepLib, (for GHC 8 compat) ought to be enough for now.
Ok. I’ve uploaded the current state of RepLib/Unbound to hackage today.
On Aug 19, 2016, at 11:43 AM, Joachim Breitner notifications@github.com wrote:
Do I need to add anything to RepLib/Unbound? Let me know.
I think uploading the current state of the repository (for GHC 8 compat) ought to be enough for now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #30 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ACAZdv92tHpVYODzob23CUZjIWKe8sDxks5qhc85gaJpZM4FzSyz.
It seems that some Example.* files were missing from the distribution, causing the test suite to fail: commercialhaskell/stackage#1794 (comment)
How do I get cabal to include those files in the distribution? They are in the github repo.
On Aug 21, 2016, at 12:16 PM, Joachim Breitner notifications@github.com wrote:
It seems that some Example.* files were missing from the distribution, causing the test suite to fail: commercialhaskell/stackage#1794 (comment) commercialhaskell/stackage#1794 (comment)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #30 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ACAZdqTSt9hlxDNA5Iw6mK5M89r6NBdTks5qiHnEgaJpZM4FzSyz.
The problem was the path name, which was lower case, and thus did not allow ghc to find the source. Fixed in #39.
Thanks!
I now get this error when I try to run cabal test. Can you help?
Stephanies-MacBook-Pro:Unbound sweirich$ cabal test
Re-configuring with test suites enabled. If this fails, please run configure
manually.
Resolving dependencies...
Configuring unbound-0.5.0...
Preprocessing library unbound-0.5.0...
on the commandline: warning:
-this-package-key is deprecated: Use -this-unit-id instead
on the commandline: warning:
-this-package-key is deprecated: Use -this-unit-id instead
on the commandline: warning:
-this-package-key is deprecated: Use -this-unit-id instead
In-place registering unbound-0.5.0...
cabal: '/Users/sweirich/local/bin/ghc-pkg' exited with an error:
unbound-0.5.0: installed package info from too old version of Cabal (key field
does not match id field)
Stephanies-MacBook-Pro:Unbound sweirich$ cabal --version
cabal-install version 1.22.6.0
using version 1.22.4.0 of the Cabal library
I now get this error when I try to run cabal test. Can you help?
This looks like a problem with your local installation. cabal-1.22 does not support GHC-8.0. Here is what Edward Yang writes about the issue:
Yes, you need to upgrade your cabal-install.
If you still have an old version of GHC around, you can upgrade using:
cabal update cabal install -w /path/to/old/ghc cabal-install
Ok. I had updated cabal, but not the one in my path. Now resolved locally and the version of unbound on hackage should have working tests.