Hi, George Danchev wrote: > These data are all known prior to ISO/jigdo creation > and are indeed better to be passed via option parameters to the producer > itself (xorriso, resp. libjte), which is not implemented yet of course. > But this is a low-priority goal, isn't it? > http://anonscm.debian.org/viewvc/debian-cd/trunk/tools/jigdo_cleanup?view=markup
I have no objections against .jigdo post-processing outside xorriso. Just wondering whether i missed a libjte release for GNU xorriso. The difference between .jigdo and libjte came up when i checked whether libisofs can in any case be to blame for the pending image verification issue. (Result: Hardly. libisofs shows its output to libjte and marks the borders of data file content. libjte is in charge of extracting .template and computing the checksums of data files and overall image.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/10043645468011@192.168.2.69
