7 Jun
2012
7 Jun
'12
8:01 p.m.
I looked in /usr/sbin/update-mime. It allows local
customization using /etc/update-mime.conf. The problem is that it is
expected to file only - not folder. Potentially, such a collision can occur
if the user will have its own configuration.
The second thing is that some files are in /opt/trinity/lib/mime/packages -
for example kate-trinity, konqueror-trinity, kdfp-trinity),
and some are in /usr/lib/mime/packages - for example kedit-trinity,
ktnef-trinity.
The location should therefore be united. And the question is
whether will be easier to use system location /usr/lib/mime or juggle the
configuration for location in /opt/trinity/lib/mime?
I don't use Chromium. Are there other apps that can help test this problem?
Second, is this a bug with update-mime more than Trinity? Or a Chromium problem?
Third, how do we build packages such that parts are installed in /usr and parts in
/opt/trinity?
Darrell