Hi all,
it seems the way we currently handle legacy mimetype registration leads
to some unwanted side effects in the recent editions of most linux vendors:
KDE 3.4 already ships with mime-type registration files the new OASIS
file types. Since we are installing similar files with different names
and there seems to be no preference handling, some of the files end up
getting the OOo icon, some the default KDE icon for that type.
So, what should we do: create those files dynamically in a postinstall
script or create version specific packages for each vendor ?
Any thoughts ?
Regards,
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
