Hi, I can see that growisofs reads GENISOIMAGE environment variable (used to be MKISOFS, as upstream does) and if there its is used as image manipulation tool. This might not be extremely convenient, but is there as a fallback.
However, we also have alternative image manipulator and burner apps like these provided by cdrskin and xorriso packages. Note, that xorriso is both image manipulator and burner application (cdrskin is burner-only) which could behave like mkisofs and few more options-wise. See -as <personality> in xorriso(1). Therefore it would make sense to just spawn 'xorriso -as mkisofs' instead of genisoimage from growisofs.c. I realize that changing the image manipulation tool to be spawned at this stage of the freeze might not be the safest thing to do, but we should do that in squeeze+1, at least. How does that sound? -- pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
