legacy/libisoburn/trunk/releng/TODO

37 lines
1.4 KiB
Plaintext
Raw Normal View History

* Invent an interpreter to read options from config files and sets the variables
or use confget ( http://devel.ringlet.net/textproc/confget/ )
2011-06-28 17:33:08 +00:00
* Write a common configuration facility.
2011-06-26 13:20:28 +00:00
2011-07-02 18:00:33 +00:00
* Merge 'merge_into_isocontent' into 'releng_isocontent' (former hardlinks)
2011-07-02 15:28:37 +00:00
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
2011-07-02 15:28:37 +00:00
result in producing an ISO image. Verify the result with:
'file'
xorriso -pvd_info
others
2011-07-07 07:58:57 +00:00
Such trivial operations could be separated in another releng_ test
which should also check other trivial operations like --devices, etc.
2011-07-02 15:28:37 +00:00
* 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 "===".
2011-07-04 17:43:15 +00:00
* 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.