37 lines
1.5 KiB
Plaintext
37 lines
1.5 KiB
Plaintext
* Invent an interpreter to read options from config files and sets the variables
|
|
or use confget ( http://devel.ringlet.net/textproc/confget/ )
|
|
OR BETTER YET TRY TO DROP the entire concept of config files and
|
|
rely solely on cmdline options.
|
|
|
|
* Write a common configuration facility.
|
|
|
|
* Expose ldd and --version of tested binary just once.
|
|
|
|
* Also support 'run_all_releng /path/to/xorriso [-keep]'
|
|
i.e. without the need to install config files in place.
|
|
|
|
* Merge 'merge_into_isocontent' into 'releng_isocontent' (former hardlinks)
|
|
Extend it to use some more demanding directory tree.
|
|
MD5s should be checked. ACLs and xattr (if we are on Linux).
|
|
All file types as of stat(2) should be tested.
|
|
|
|
* Also check trivial operations like --devices, etc.
|
|
|
|
* Split off common functionality in common ./lib/ so it can be re-used
|
|
by all scripts. This might include cmdline option parsing, some
|
|
validation code like releng_isocontent:is_valid_iso9660
|
|
|
|
* We need to give a hint about how much storage space will be consumed.
|
|
|
|
* We could mark all own stderr messages by a prefix like "===".
|
|
|
|
* Burning tests ideas/thoughts by Thomas:
|
|
> There will have to be a warning and user input before we load
|
|
> the drive tray. -dev, -indev, -oudev do this loading which can
|
|
> cause finger injury, psychical trauma, and chuting computers.
|
|
>
|
|
> Further if we want to have a burn test (with MD5 and checkreading)
|
|
> then we will need configuration means to enable this. By default
|
|
> it should not risk to burn one-time media which sit in the drive
|
|
> by mere accident.
|