b14 will private beta after all.
While I'm pretty confident in basic test functionality (my reason for
thinking of jumping to open beta), I've rethought the features, helper
tools needed and potential ass-ache of automated cleanup if needed for
various configs if I missed something. Based on lack of feedback, it
shouldn't be an issue.
b14 password will be per chain.
Once I feel I have a feature complete rc1, I'll most likely do the open
beta. Given the lack of response, I wonder if it's worth the extra
effort to make the script more robust for environment/helper
tool/configuration error checking, fallback and management. All these
things are easier to handle manually if you know what you're doing, but
suck a lot of time and effort to try to handle in the script.
Added features:
- cached helpers tools (similar to app bundle) with backup/restore and
verification on run
- optionally test jpeg/png files in archives (no need for embedded sfv/par)
- optionally report statistics per archive: min/max/avg image
size/resolution/color depth (script already logs numbers of files by
type: JPG/PNG/WEBP/TXT/ETC)
Both file image test/statistics features require de-archiving and are
therefore expensive in terms of disk utilization/time, but automate
what could be done manually (as is the gist of the entire script).
Rebuilding archives will include image checks and error handling by
default.
symm
|
| Follow-ups: | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | 31 | 32 | 33 | 34 |
|