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

Mention the difference between dev_signed and release binaries in FAQ #1110

Open
krystian-hebel opened this issue Oct 25, 2024 · 1 comment
Labels
doc documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers

Comments

@krystian-hebel
Copy link

No description provided.

@krystian-hebel krystian-hebel added documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers doc labels Oct 25, 2024
@zirblazer
Copy link

Highly reelevant to this, in chat there were multiple people that have asked about the sha256 of the binaries you build yourself being wrong because the build instructions produces a binary with the same name than the one you get from Dasharo suscription, whereas the one you build yourself correspond to the dev_signed version. So perhaps you want the default filename to include dev_signed, or make it the default and make the suscription binary name different or whatever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc documentation Improvements or additions to documentation enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants