dsum
| Crates.io | dsum |
| lib.rs | dsum |
| version | |
| source | src |
| created_at | 2025-01-13 11:42:36.627008+00 |
| updated_at | 2025-01-13 11:42:36.627008+00 |
| description | Checksum for directories |
| homepage | |
| repository | https://codeberg.org/nightsail/dsum |
| max_upload_size | |
| id | 1514534 |
| Cargo.toml error: | TOML parse error at line 21, column 1 | 21 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Blair Noctis (nc7s)
documentation
README
dsum: directory checksum
Like md5sum(1) and shasum(1), but for directories. It calculates a sum list just like md5sum, then sums that as if the directory is a file with that as content.
For now, install with cargo install dsum.
Multiple hashing algorithms are supported. By default BLAKE3 is used, due to its speed.
For convenience, dsum(1) can be invoked as b2dsum, b3dsum, sha1dsum, etc. and directly use the named algorithm. cargo install does not support this kind of "installation", the install-aliases.sh script might be helpful.
Inspired by David Tolnay's sha1dir, which uses a clever trick of XORing checksums of each directory entry into one. However these checksums are calculated differently from traditional *sum(1)s, plus also hashing in file modes, which might not be desirable.