Hi all,
Chromium on my machine suddenly began to open PDF files in the GV. I began to wonder why and found that they follow entries in the file /etc/mailcap. It is generated automatically by update-mime using files in /usr/lib/mime. But some files are installed into /opt/trinity/lib/mime.
I think we should fix that instead of /opt/trinity/lib/mime were all installed in /usr/lib/mime. What do you think?
Slavek --
Chromium on my machine suddenly began to open PDF files in the GV. I began to wonder why and found that they follow entries in the file /etc/mailcap. It is generated automatically by update-mime using files in /usr/lib/mime. But some files are installed into /opt/trinity/lib/mime.
I think we should fix that instead of /opt/trinity/lib/mime were all installed in /usr/lib/mime. What do you think?
Does update-mime have a global/system configuration file to add alternate mime directories?
Darrell
On Thursday 07 of June 2012 19:17:36 Darrell Anderson wrote:
Chromium on my machine suddenly began to open PDF files in the GV. I began to wonder why and found that they follow entries in the file /etc/mailcap. It is generated automatically by update-mime using files in /usr/lib/mime. But some files are installed into /opt/trinity/lib/mime.
I think we should fix that instead of /opt/trinity/lib/mime were all installed in /usr/lib/mime. What do you think?
Does update-mime have a global/system configuration file to add alternate mime directories?
Darrell
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?
Slavek --
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
On Thu, 7 Jun 2012 13:01:01 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
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?
Fourth, is this distro-specific? My system has neither update-mime nor /usr/lib/mime, suggesting that this utility is not universal.
Fourth, is this distro-specific? My system has neither update-mime nor /usr/lib/mime, suggesting that this utility is not universal.
Yes, this is Debian-specific.
Slackware has update-mime-database, which is why I asked for other apps besides Chromium to test the problem. If this is distro-specific perhaps we at least could share how to replicate and also resolve the problem, and which distros are/might be involved.
Darrell
On Friday 08 of June 2012 00:28:21 Darrell Anderson wrote:
Fourth, is this distro-specific? My system has neither update-mime nor /usr/lib/mime, suggesting that this utility is not universal.
Yes, this is Debian-specific.
Slackware has update-mime-database, which is why I asked for other apps besides Chromium to test the problem. If this is distro-specific perhaps we at least could share how to replicate and also resolve the problem, and which distros are/might be involved.
Darrell
Specific for distribution may be a way of composing /etc/mailcap. But its meaning is common to all. It affects generally all programs that uses /etc/mailcap. For testing can be used (ie Debian) commands such as run-mailcap, see, print, compose,...
The truth is that the file location is apparently a matter of packaging == distribution specific. I just now looking into the packages and kpdf-trinity and kedit-trinity. That differ not only in the location: /usr/lib/mime × /opt/trinity/lib/mime, but also /usr/share/menu × /opt/trinity/share/menu, /usr/share/doc/kedit-trinity × /opt/trinity/share/doc/kpdf-trinity.
Obviously it is a mess. :)
Slavek --
On 7 Jun 2012, Darrell Anderson outgrape:
Fourth, is this distro-specific? My system has neither update-mime nor /usr/lib/mime, suggesting that this utility is not universal.
Yes, this is Debian-specific.
Slackware has update-mime-database, which is why I asked for other apps besides Chromium to test the problem. If this is distro-specific perhaps we at least could share how to replicate and also resolve the problem, and which distros are/might be involved.
update-mime-database is a completely different tool, part of upstream shared-mime-info. (Yes, I know the names are very confusing.)
update-mime-database is a completely different tool, part of upstream shared-mime-info. (Yes, I know the names are very confusing.)
Ah, okay, thanks. Your reply prompted me to find this:
http://man.he.net/man8/update-mime
That information implies update-mime is a Debian tool only.
Darrell
In article 201206071911.59927.slavek.banko@axis.cz, Slávek Banko trinity-devel@lists.pearsoncomputing.net wrote:
Hi all,
Chromium on my machine suddenly began to open PDF files in the GV. I began to wonder why and found that they follow entries in the file /etc/mailcap. It is generated automatically by update-mime using files in /usr/lib/mime. But some files are installed into /opt/trinity/lib/mime.
I think we should fix that instead of /opt/trinity/lib/mime were all installed in /usr/lib/mime. What do you think?
ISTR opening a bug on this area. Let me check a minute.
Note that Debian is slowly ceasing to ship mailcap compatible entries unless a rearguard action to maintain them gets going :)
Nick
-
Darrell Anderson -
E. Liddell -
Nick Leverton -
Nix -
Slávek Banko