GNOME Bugzilla – Bug 144953
ISO reading assumes Joliet and Rock Ridge extensions
Last modified: 2005-02-27 19:42:40 UTC
Currently the iso reading code assumes that the iso file has the Joliet and Rock Ridge extension on, which can result in errors or bad file names if the iso dosn't have them. The way to solve this is that the isoinfo program needs to be run twice. The first time to see what extensions the iso supports, and the seconds to actually do the listing/extracting. The problem is that the arguments for the second program depend on the result from the first program. It seems that the fr_process_start does not start immideatly but delays it for later execution, meaning I can't use it to actually get the results I need before setting the parameters for the second command. I believe the only way to do this is to create a new FrProcess for getting the supported iso extensions before using the FrCommand's FrProcess for doing the work. Is there a more 'correct' way to do this, or is this the right way to do this?
The Debian BTS has a bug report about this too: http://bugs.debian.org/267172 "File Roller cannot open an .iso that does not have the Joliet extensions. I discovered this when attempting to view the linux.iso that ships with VMware, containing the vmware-tools. There is a library called libiso9660 in Debian that may simplify supporting ISO-9660 file systems in File Roller. Perhaps you can forward that information upstream?"
Using the libiso9660 (or upstream called libcdio) sounds like a good idea. I will try later on when I have more free time (I hope soon) to see if I can convert it easily to use the library
Bug 160769 is a dupe of this bug? Still appears to be in file-roller-2.8.1.
*** Bug 160769 has been marked as a duplicate of this bug. ***
fixed in current CVS.