Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

autumnontape · 2024-09-18 22:21:44

I maintain the `gargoyle` AUR package, and I've just adopted the `qtads` package as well. These applications both open TADS 2 & 3 story files, and they both provide icons for the corresponding MIME types in `/usr/share/icons/hicolor/32x32/mimetypes`.

The icons provided by the two packages conflict with each other; and they differ, too, though I don't think it would be a problem if Gargoyle's icons were used when the `qtads` package was installed. The reverse might be questionable, since Gargoyle uses the same icon for many interactive fiction story formats, so TADS 2 & 3 files would be the only ones that looked different if the QTads icon were used for them.

My best idea to resolve this right now is to put the icons in a separate package named `gargoyle-icons` and list that package as a dependency of both `gargoyle` and `qtads`. Does anyone have a better alternative? Is there a way to let the packages install their icons in different places, ideally with Gargoyle's icons being chosen when both are installed?

I haven't pushed an update to `qtads` yet because I want to resolve this conflict first. These two packages also both provide MIME type database entries for these two types of file, which are identical aside from their "comment" fields. This at least doesn't seem like a problem.

As a side question: QTads has a built-in update checker. By default, it's configured to check for updates once a day. Should I patch the default setting to "never check for updates" when packaging it? It always bothers me when an application I've installed through a package manager automatically checks for updates.

seth · 2024-09-19 07:07:34

put the icons in a separate package named `gargoyle-icons` and list that package as a dependency of both `gargoyle` and `qtads`

Unless you can/want to mutually conflict the gargoyle and qtads package, that's what you'll have to do.

patch the default setting to "never check for updates"

because

It always bothers me when an application I've installed through a package manager automatically checks for updates.

notably since they're not applicable.

autumnontape · 2024-09-20 05:37:47

All right. I was hoping someone with freedesktop.org knowledge might have a secret that would let me avoid making a third package. But I'll split it up tomorrow and push a qtads update, unless that person shows up between now and then.

seth · 2024-09-20 07:30:44

fdo.org means you're looking for different icon files (no package conflict) and a way to control extension/icon resolution preference?
https://unix.stackexchange.com/a/419926

autumnontape · 2024-09-22 19:18:45

seth wrote:

fdo.org means you're looking for different icon files (no package conflict) and a way to control extension/icon resolution preference?
https://unix.stackexchange.com/a/419926

I don't really need to be able to control the resolution process, but yes, that's the kind of solution I had in mind. It's not possible to install hicolor icons for the same MIME type without conflicts as far as I've been able to tell, which is extremely unfortunate, since adding MIME types to the shared MIME-info database without conflicts is perfectly possible.

seth · 2024-09-22 19:44:45

Ah, the mediatype is "application" and "application-x-generic" would be wrong

A more disgusting approach could be to ship disjunct files in the packages and use post-install scripts to conditionally symlink them into place, but that's probably gonna messy on partial removal.
A 3rd package will be the much cleaner approach.

autumnontape · 2024-09-22 19:47:51

Yeah... I think I'm going to use a split PKGBUILD for each package, providing X and X-icons for each, with gargoyle having gargoyle-icons as an optional dependency, and qtads having both gargoyle-icons and qtads-icons as optional dependencies. It's pretty painful, especially for AUR packages.

Arch Linux

#1 2024-09-18 22:21:44

Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

#2 2024-09-19 07:07:34

Re: Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

#3 2024-09-20 05:37:47

Re: Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

#4 2024-09-20 07:30:44

Re: Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

#5 2024-09-22 19:18:45

Re: Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

#6 2024-09-22 19:44:45

Re: Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

#7 2024-09-22 19:47:51

Re: Conflicting files in /usr/share/icons/hicolor/32x32/mimetypes

Board footer