chandler is a tool for software developers to normalize application tape archives (*.TGZ, *.TAR.GZ files).
$ cd example
$ tree -p hello-1.0.0
[drwxr-xr-x] hello-1.0.0
├── [-rw-r--r--] hello
├── [-rw-r--r--] hello.bat
└── [-rw-r--r--] README
1 directory, 3 files
$ chandler -czf hello-1.0.0.tgz hello-1.0.0
archived entries to hello-1.0.0.tgz
$ tar -tzvf hello-1.0.0.tgz
drwxr-xr-x 0 501 20 0 Nov 14 11:18 hello-1.0.0
-rw-r--r-- 0 501 20 186 Nov 13 14:48 hello-1.0.0/README
-rwxr-xr-x 0 501 20 31 Nov 13 14:35 hello-1.0.0/hello
-rw-r--r-- 0 501 20 22 Nov 13 14:34 hello-1.0.0/hello.batAbove, chandler aligns target file metadata to industry standards, repairing glitches in source file metadata.
See CONFIGURATION.md for configuration file options.
Run chandler -h for CLI options.
chandler automates industry norms for file permissions, file exclusions, lexicographical sorting, file path normalization, and more.
Metadata is normalized as each entry enters the archive, regardless of the original file metadata. This smooths out common SDLC workflows, especially for multi-platform engineering teams.
https://crates.io/crates/chandler
https://docs.rs/chandler/latest/chandler/
https://github.com/mcandre/chandler/releases
$ cargo install --force --path .(None)
- a UNIX-like environment (e.g. WSL)
- case sensitive or case aware file systems (e.g. ext4, exFAT, APFS, NTFS)
- GNU/BSD/Windows tar with gzip support
- tree
For more details on developing unmake itself, see DEVELOPMENT.md.
BSD-2-Clause
📼