On Wed, May 13, 2009 at 09:38:17AM +0200, Yves-Alexis Perez wrote: > On mer, 2009-05-13 at 08:29 +0200, Yves-Alexis Perez wrote: > > The current mime.cache version, according to the spec, is > > 1.1 but my /usr/share/mime.cache seems to still be 1.0: > > > > hexdump /usr/share/mime/mime.cache |head -n1 > > 0000000 0100 0100 0000 d441 0000 d046 0000 0c56 > > Uh, oh, wait, the version is on 16 bit, so I indeed have 1.1, which is > then not used at all by thunar. So we're kind-of safe for the moment, > but at one point the check should be added to be able to read 1.1 files. > Though I'm not sure changing the filename is a good idea, and yeah, why > not putting the version check in the code so apps can use “old” and > “new” formats? > > Cheers,
As already said, the whole format is already versioned by definition, so the proper fix is - at application level - supporting both formats. Changing file name is NOT a proper fix, is a bad/pointless workaround for badly written programs. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
