There's already plenty of console ROM types in shared-mime-info. To add more, please make sure to contribute the new items upstream, following the HACKING file in the shared-mime-info git repository. ----- Original Message ----- > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > hi > I'm in agreement with this. This makes a lot of logical sense. i was > hoping to improve the mime info for lots of video game rom types, but > that's outside the scope of this message. > Thanks > Kendell clark > > > Kevin Fenzi wrote: > > Greetings. > > > > For a while now it's been possible for desktops to have their own > > mime info (which is great), but it seems we have also gotten rid of > > the generic one, which causes some strange behavior: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1243049 > > > > ie, /usr/share/applications/defaults.list no longer exists, and > > shared-mime-info ships just a: /usr/share/applications/gnome.list > > > > This leads to issues with tools that don't happen to be run under > > gnome. Of course other desktops can (and probibly should) make > > their own lists, but IMHO we should also have a generic one for > > tools not running under any particular DE. > > > > So, my questions: > > > > 1. Can we add back a defaults.list ? > > > > 2. Should other DE's ship their lists also in shared-mime-info or > > should they provide it as part of some other base package? On the > > one hand one place might be nice, on the other it would make > > shared-mime-info update more often and sometimes for things that > > don't affect you. > > > > Thanks for any thoughts... > > > > kevin > > > > > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCgAGBQJVptL5AAoJEGYgJ5/kqBTd6f4P/2w0cFN6M9EbX/dnZ4B0yrCD > AdM5dIn2a8D+MHZMJk0e2BT9LupzGHUvAF9EJsnV7ZnXUH/xwDtQz5KnM/WCOzzF > 1T8eC1tVuyp5UGG9RrsDHxqrWFoFzwmfLqCPROS9kOxcoBNgd9TVWQmKIzW46W2Z > CwWwpMxV34TtwJJislQAHnslQ1nYuaZKms9u9q7sPBkl5bzYjVvuQ7W9XvZFqGGj > XtjQ/1qaxyURcxxolsg4x4Ay1Cs2CW4W7xJWA2Aw2phiaQ718opEf1bqDyfZVYDQ > aviYNj7LsNj6NDA6uYcYTLVrSbS1PwUPhxrwKRQJo80pvicGZ+B8Py17J3EWwTry > CXQZmUJFey55uNgW9yTS4j+g7ZRchm6uDXZgK3YIZr/Sugxs5DjHy2wol2YY7C6j > 9zGF8xoGwYWnjlWBcQJiIBhMzL4xOc/5ss+Jsjx26E4OPJLPbVqsyUZD3m8ss9ig > aHsCgIRvjWFHLyJPEXpmnO6jMB/aFZdCsJfnuIarvUJumK8eqnP7GNJRADgDkqAK > hkbIDbyRKwklNChXW+59G805IkyEI+MJG6URBRjdyeUvDB3ngogxHdiSI+t/y82t > DsU6k+jZlrg/1yCWm4p4jiuUYVmH0U44OxlZzorxbpWfGxvCeG63iuQ3vLfWiuPJ > tJqd5mUFEs2nB+pt5T1j > =ZRF1 > -----END PGP SIGNATURE----- > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
