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
kiconthemes: KIconTheme needs to add BreezeIcons as build-time dependency and needs to be patched for init icon resources correctly #20687
Comments
breeze and breeze-icons are incomplete right now because the source tarball contain symlinks. craft uses some wizardry to copy files, see https://invent.kde.org/packaging/craft/-/blob/bfac5fa33be1ae8a4be2e9a9446a9aa05fc103fc/bin/utils.py#L153-153. I need some help to fix those first. |
Is there a related issue so I can check the details?
I'm interested in helping (no promise tho, since my spare time is quite limited recently), but is that issue blocking this issue from fixed? If not, I personally tend to fix this issue first when I got time, then try the symlink one. |
Additionally, I actually didn't even notice the missing icon issue. KDE apps on Windows actually use the BreezeIcon assets embedded in the resource file instead of using the one on-disk. Do you have related screenshots (or other info/resources) to showcase this issue? |
Thanks! Also put a link here so people could find related info: https://cullmann.io/posts/kde-applications-and-icons/ |
Description / Steps to reproduce the issue
There are two issues:
And another issue I haven't figure it out right now:
Expected behavior
kiconthemes is build with BreezeIcons and patched, so KDE apps like Kate can find breeze icons, as lone as they are depend on kiconthemes.
Actual behavior
kiconthemes (currently
ucrt64/mingw-w64-ucrt-x86_64-kiconthemes 6.1.0-1
) is not build with BreezeIcons and not patched.Verification
Windows Version
MINGW64_NT-10.0-22631
MINGW environments affected
Are you willing to submit a PR?
Maybe? But might not have time to submit this as a patch right now. Feel free to work on it directly if you plan to do so, and please leave a comment first before you work on this issue.
The text was updated successfully, but these errors were encountered: