Browse Source

drop completed todo items; cleanups

master
George Danchev 11 years ago
parent
commit
e1aa125c05
  1. 4
      releng/TODO
  2. 4
      releng/releng_printsize
  3. 2
      releng/template_new_releng

4
releng/TODO

@ -1,6 +1,4 @@
* Expose xorriso --version of tested binary just once.
* 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).
@ -10,8 +8,6 @@
xorriso --devices
xorriso -indev file.iso -pvd_info
* 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

4
releng/releng_printsize

@ -5,7 +5,7 @@ set -e
# Include common bits
. inc/releng_getopts.inc
# Each releng_ test should decide whether or not it need
# Each releng_ test should decide whether or not it needs
# a xorriso binary to test, since some do compilations only.
if [ ! -x $RELENG_XORRISO ]; then
print_help
@ -26,6 +26,8 @@ fi
UPPER=40
# All must be set at this point
# TODO: work out a smarter way to quickly generate different
# types of trees (long, deep, etc)
printf "\n${SELF}: Generating sample tree in ${GEN_DATA_DIR}..."
for ((i1=0; i1 < ${UPPER}/4; i1++))
do

2
releng/template_new_releng

@ -7,7 +7,7 @@ set -e
printf "\n$0: FAIL: === TEPLATE === RENAME ME TO releng_<title>\n"
# Each releng_ test should decide whether or not it need
# Each releng_ test should decide whether or not it needs
# a xorriso binary to test, since some do compilations only.
if [ ! -x $RELENG_XORRISO ]; then
print_help

Loading…
Cancel
Save