diff options
| author | merakor <cem@ckyln.com> | 2021-07-30 13:49:07 +0000 |
|---|---|---|
| committer | merakor <cem@ckyln.com> | 2021-07-30 13:49:07 +0000 |
| commit | f70e7cc170ca3455140ac8523edd912fce4d4ca3 (patch) | |
| tree | 966a7ea536034d9b3e100fb3b55508d0513ed729 | |
| parent | aab6f5bc18810b340515d5e9decaadb144c84b15 (diff) | |
| download | cpt-f70e7cc170ca3455140ac8523edd912fce4d4ca3.tar.gz | |
docs: update
FossilOrigin-Name: ffbb030782309ac3283f5686721fabc345ab290b0ec8ec83a951c1215db50dca
| -rw-r--r-- | CHANGELOG.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index c90e9d0..16fc326 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -12,6 +12,25 @@ this project _somewhat_ adheres to [Semantic Versioning]. [Unreleased] -------------------------------------------------------------------------------- +### BLAKE3 checksums + +The package manager now uses `b3sum` for creating digests. The change is +backwards compatible, which means that BLAKE3 will slowly replace the SHA256 +algorithm in packages. The `cpt` package in the repository will continue to use +the sha256 until the end of 2021. + +The `checksums` files generated with BLAKE3 has the header `%BLAKE3` which is +used to distinguish digest algorithms. If the file does not include such a +header, it is assumed to be a file created using the SHA256 algorithm. This is +especially handy for keeping the /etc checksums intact. If the package being +built is already installed on the system `cpt` makes sure that the generated +etcsums are also backwards compatible. + + +### Added +- `cpt-checksum` now has the `-s` flag to generate checksums using the SHA256 + digest algorithm. + ### Changed - `cpt-size` has been rewritten to support POSIX `du`, and to support packages with a file count of over 50,000. |