forked from kiss-community/kiss
51768ad4c3
As discussed in kiss-community/repo#100 and #39, we seem to be in favor of switching to blake3. The following changes are made: - All newly generated checksums are blake3 - The user is prompted to generate blake3 checksums if sha256 sums are present (maybe this should be automatic) - For installed packages, we can fall back to sha256 to check etcsums This includes a name change of the `checksums` and `etcsums` files -- I'm not sure of any better way to detect whether sha256 sums are in use, as blake3 sums are the same length. Feedback is appreciated Co-authored-by: Owen Rafferty <owen@owenrafferty.com> Reviewed-on: https://codeberg.org/kiss-community/kiss/pulls/72 |
||
|---|---|---|
| .github | ||
| contrib | ||
| kiss | ||
| LICENSE | ||
| README | ||
|/ |\ISS LINUX https://kisslinux.org ________________________________________________________________________________ Package Manager ________________________________________________________________________________ KISS' tiny package manager. Documentation: - https://kisslinux.org/package-manager - https://kisslinux.org/package-system