legacy/libisoburn/trunk/releng/TODO
2011-07-07 09:42:01 +00:00

40 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/ )
* Write a common configuration facility.
* 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 (in releng_isocontent) simple operations like:
xorrisofs foo/ > foo.iso
xorrisofs foo/ -o foo.iso
xorrisofs foo/ | cat > foo.iso
result in producing an ISO image. Verify the result with:
'file'
xorriso -pvd_info
others
Such trivial operations could be separated in another releng_ test
which should also check other trivial operations like --devices, etc.
* 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.