drop CXX completed item, add simple operation item

releng/TODO

@@ -7,10 +7,20 @@
   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
+
 * 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 "===".
+* 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
@@ -22,31 +32,3 @@
   > it should not risk to burn one-time media which sit in the drive
   > by mere accident.
 
-* C++ cleanness - hopefully store C++ samples code in aux/ directory
-  in order to avoid C++ code generation from the shell script test,
-  which would be cumbersome
-
-$ g++ -I ../libisoburn -L ../libisoburn/.libs/ -lisoburn -o cxx cxx.cpp
-
-#include <iostream>
-#include <inttypes.h>
-
-#if __WORDSIZE == 32
-#define _LARGEFILE_SOURCE 1
-#define _FILE_OFFSET_BITS 64
-#endif
-
-#include "libisoburn/xorriso.h"
-
-using namespace std;
-
-int main()
-{
-   cout 
-     << " major:" << Xorriso_header_version_majoR
-     << " minor:" << Xorriso_header_version_minoR
-     << " micro:" << Xorriso_header_version_micrO
-     << endl;
-
-   return 0;
-}