-
Notifications
You must be signed in to change notification settings - Fork 691
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.
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
Don't depend on hashable
directly
#10140
Comments
ulysses4ever
added
type: enhancement
attention: pr-welcome
newcomer: 3-multi-file-refactor
newcomer
and removed
type: bug
needs triage
labels
Jun 24, 2024
jaspervdj
added a commit
to jaspervdj/cabal
that referenced
this issue
Sep 5, 2024
2 tasks
jaspervdj
added a commit
to jaspervdj/cabal
that referenced
this issue
Sep 5, 2024
jaspervdj
added a commit
to jaspervdj/cabal
that referenced
this issue
Sep 5, 2024
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AFAICT, the
hashable
is used for semi-persistent, low-rate hashing. Thehashable
is not designed for that:You'd be better of to use e.g. https://hackage.haskell.org/package/cryptohash-sha256 on which
cabal-install
depends throughhackage-security
anyway.Clarification: the usage is persistent, if the user happens to have even the same
cabal-install
version compiled against the differenthashable
versions; they won't find the same local files / caches. Don't usehashable
for persistence.The text was updated successfully, but these errors were encountered: