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.

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

Preserve hashes #12

Open
davidak opened this issue Oct 18, 2019 · 0 comments
Open

Preserve hashes #12

davidak opened this issue Oct 18, 2019 · 0 comments

Comments

@davidak
Copy link
Collaborator

davidak commented Oct 18, 2019

If i understand correctly, the package hashes are lost after comparison.

Until we have some infrastructure to submit them, i suggest a pragmatic solution and just save them in a CSV file or no-sql db.

What datastructure do we need?

I spontaneously think of:

  • timestamp of hash calculation
  • nix store path of the package
  • maybe package name for better human readability
  • the hash of the built package
  • name of submitter

How could we be sure that it's actually built by the submitter? Sign it with PGP like git?

When we have infrastructure to submit the data (that could be a very simple webapp with nosql backend), we can just upload the data that we preserve now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant