Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support icons from libraries for deb and rpm #4104

Merged
merged 2 commits into from
Jun 7, 2024

Conversation

HebaruSan
Copy link
Member

Motivation

In the course of discussing #4073, it dawned on me that Linux systems support icon themes, and typical .desktop files enable this by using a symbolic name for their icons instead of an absolute path. So I spent a while reading up on how that works:

Changes

  • Now the .desktop files use the symbolic name Icon=ckan instead of the absolute path Icon=/usr/share/icons/ckan.ico, to allow icon libraries to supply their own custom icons for CKAN
  • Now the deb and rpm packages no longer install /usr/share/icons/ckan.ico; instead, they install our variously sized ckan-16.png, ckan-32.png, ... , ckan-256.png files to /usr/share/icons/hicolor/16x16/apps/ckan.png (and so on for all the sizes), because this is the path for default application-supplied icons according to the spec

@HebaruSan HebaruSan added Enhancement Build Issues affecting the build system Linux Issues specific for Linux Package: deb Issues affecting the Debian packaging Package: rpm Issues affecting RPM packaging labels Jun 7, 2024
@HebaruSan HebaruSan merged commit e92777c into KSP-CKAN:master Jun 7, 2024
3 checks passed
@HebaruSan HebaruSan deleted the feature/linux-icon-libs branch June 7, 2024 03:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Issues affecting the build system Enhancement Linux Issues specific for Linux Package: deb Issues affecting the Debian packaging Package: rpm Issues affecting RPM packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant