Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

why not "cabal install cryptol"? #18

Closed
LeventErkok opened this issue Apr 27, 2014 · 8 comments
Closed

why not "cabal install cryptol"? #18

LeventErkok opened this issue Apr 27, 2014 · 8 comments
Assignees
@acfoltzer
Labels
feature request Asking for new or improved functionality
Milestone
Cryptol 2.2

Comments

@LeventErkok
Copy link
Contributor

well this is not a real bug, but I don't see why we can't just "cabal install cryptol"

at least the Haddock'ed sources should be hosted somewhere for us to browse, as browsing thru github is rather painful.
@kiniry kiniry added this to the Cryptol 2.1 milestone Jun 23, 2014
@kiniry
Copy link
Member

kiniry commented Jun 23, 2014

We'd like to roll this out once we have the proper cabal dependency straightened out between Cryptol and SBV.

@kiniry kiniry mentioned this issue Jun 23, 2014
Closed
@kiniry kiniry modified the milestones: Cryptol 2.2, Cryptol 2.1 Sep 23, 2014
@kiniry
Copy link
Member

kiniry commented Sep 23, 2014

Also depends upon #112.

@acfoltzer acfoltzer self-assigned this Feb 19, 2015
@LeventErkok
Copy link
Contributor Author

Well; not fair to close this until I can actually do a "cabal install cryptol" and get it from Hackage!

@acfoltzer
Copy link
Contributor

Heh, good point! It's now just waiting on the 2.2 release, but I'll keep it open as a reminder.

@acfoltzer acfoltzer reopened this Mar 10, 2015
acfoltzer pushed a commit that referenced this issue Mar 10, 2015
switch to TH solution for GitRev
b060967 
This helps with #18 and should also reduce the number of unnecessary
recompiles that were triggered by the Makefile and/or cabal
acfoltzer pushed a commit that referenced this issue Mar 16, 2015
switch to TH solution for GitRev
a46b4c3 
This helps with #18 and should also reduce the number of unnecessary
recompiles that were triggered by the Makefile and/or cabal. The cabal
build type is now Simple.

Most of the complication in the TH.hs module is due to the various
places the current git hash might be stored:

1. Detached HEAD: the hash is in `.git/HEAD`
2. On a branch or tag: the hash is in a file pointed to by `.git/HEAD`
in a location like `.git/refs/heads`
3. On a branch or tag but in a repository with packed refs: the hash is
in `.git/packed-refs`

These situations all arise under normal development workflows and on the
Jenkins build machines, but there might be further scenarios that cause
problems. The tradeoff seems worthwhile though as now projects that
build Cryptol as a dependency wind up having to rebuild Cryptol far less
frequently.
@LeventErkok
Copy link
Contributor Author

@acfoltzer SBV 4.2 is out on Hackage.. I'm waiting for being able to say "cabal install cryptol"..

@LeventErkok
Copy link
Contributor Author

Well.. 1+1 finally equals 0 again, fresh from Hackage.. Time to close this ticket.. This was a long time coming, congrats to the whole team!

$ cabal install cryptol
Resolving dependencies...
Downloading GraphSCC-1.0.4...
Downloading ansi-terminal-0.6.2.1...
Configuring ansi-terminal-0.6.2.1...
Downloading gitrev-1.0.0...
Downloading heredoc-0.2.0.0...
Configuring GraphSCC-1.0.4...
Configuring gitrev-1.0.0...
Downloading monadLib-3.7.3...
Configuring heredoc-0.2.0.0...
Downloading presburger-1.3.1...
Downloading smtLib-1.0.7...
Downloading utf8-string-1...
Building GraphSCC-1.0.4...
Building heredoc-0.2.0.0...
Building gitrev-1.0.0...
Building ansi-terminal-0.6.2.1...
Installed heredoc-0.2.0.0
Configuring presburger-1.3.1...
Configuring monadLib-3.7.3...
Installed gitrev-1.0.0
Building presburger-1.3.1...
Configuring utf8-string-1...
Installed GraphSCC-1.0.4
Building monadLib-3.7.3...
Building utf8-string-1...
Configuring smtLib-1.0.7...
Installed ansi-terminal-0.6.2.1
Building smtLib-1.0.7...
Installed utf8-string-1
Installed monadLib-3.7.3
Installed presburger-1.3.1
Installed smtLib-1.0.7
Downloading cryptol-2.2.0...
Configuring cryptol-2.2.0...
Building cryptol-2.2.0...
Installed cryptol-2.2.0
cabal install cryptol  178.91s user 12.76s system 102% cpu 3:07.32 total
$~>cryptol
                        _        _
   ___ _ __ _   _ _ __ | |_ ___ | |
  / __| '__| | | | '_ \| __/ _ \| |
 | (__| |  | |_| | |_) | || (_) | |
  \___|_|   \__, | .__/ \__\___/|_|
            |___/|_|  version 2.2.0

Loading module Cryptol
Cryptol> 1+1
Assuming a = 1
0x0

@LeventErkok
Copy link
Contributor Author

Well; just noticed haddock choked on it.. Who knows why.. Might be a good idea to push the docs separately onto hackage. (There's a way to do that: http://neilmitchell.blogspot.com/2014/10/fixing-haddock-docs-on-hackage.html I haven't tried it myself, but it comes from a trusted source!)

@acfoltzer
Copy link
Contributor

It was a mistake in our Haddock syntax, thus the 2.2.1 release. D'oh! Now cabal haddock is part of our build script so it hopefully won't happen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@acfoltzer acfoltzer

Labels
feature request Asking for new or improved functionality
Projects
None yet
Milestone
Cryptol 2.2
Development

No branches or pull requests
3 participants
@acfoltzer @kiniry @LeventErkok