Introduces the -z <max_cmp_size> flag, enabling users to set a custom file size limit for pre-installation change checks and avoiding future hard-coded limit modifications.
Details
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
I'd suggest to split the default increase and the added new option into two separate commits.
The commit that increases the default should have some data to back the decision made. E.g. installworld time decreased by that many seconds.
| usr.bin/xinstall/install.1 | ||
|---|---|---|
| 269–274 | I think wording can be improved here. Subscribing an expert. | |
"installworld time" can't be resquied due to the build of the llvm and its libs :D
But IMO, -C is not for the time reduction (at least it is less important), rather to keep unchanged parts w/o overwriting. Reduce flash writes, keep changes visible, etc.
-C for builds makes a lot of sense.
I think we should remove the limit all together. It was added in originally because mmap was being used in commit de264c2bd89b931303db40fb8a50c9ee5ed8f858.
Updates the install's maximum file size of a file to select it for comparison with the -C flag.
Update revision: https://reviews.freebsd.org/D57503
Bryan, can you please review it too?
Thanks!