Open Scotty-Trees opened 2 years ago
Hey, thanks for the bug report :) It seems like the package extension-manager
installs a icon with the same name as one by cozy. I'll need to have a look how this can be fixed. Until then, I suggest to use the Flatpak.
Glad you like Cozy :)
No worries, I'll keep an eye on this. Let me know if you need any additional information or any testing for any fixes. Till then good luck!
The same issue (clash with gnome-shell-extension-manager) is present in Ubuntu 22.04, when one tries to install Cozy from the PPA.
Thanks, I haven't had much time but will hopefully have a look at it soon
Hi, we've recently came across this as well, in the Fedora Linux distro.
It seems that some of the icons shipped by cozy come from the Gnome Icon Library. From a packaging perspective, this is good news, since the conflicts could be solved by putting the GIL icons in a separate package, and then adding it as a dependency of cozy.
However, not all icons seem to originate from the Gnome Icon Library. Which raises two questions: 1) Where do they come from? 2) What's their licence?
The GIL icons are licensed CC0, which most distros consider OK for content.
Hi @suve, packaging GIL as a separate package sounds like a good idea! But I'm not sure how to handle this situation if Fedora is the only one providing this package. For all other distributions Cozy would still need to provide the icons itself. Is there a way to install the icons at a place where only Cozy can use them and no conflicts can happen?
Regarding your other questions: All icons not originating from GIL are originated from here: https://materialdesignicons.com/ (or on Github https://github.com/Templarian/MaterialDesign). They are released under the Apache 2.0 licence. I believe this is fine for most distros?
Hello, (for context, I'm the one who reported the conflict to @suve, and proposing a common package for these icons in Fedora)
When I researched this, I discovered that this problem was handled in three different ways by other apps:
1- Using gresource file, which would basically "hardcode" the icon into the app
2- By preceding the icon name with the app name or uuid, in a namespace kind of way
3- By installing those icons in /usr/share/name_of_the_app/icons/hicolor/...
But I'm not sure how to handle this situation if Fedora is the only one providing this package.
As for me, cozy can keep providing and installing these icons - I'd just remove them during the packaging process and add GIL as a dependency.
Alternatively - I haven't really worked with GTK before, so I don't know if it's even feasible - but maybe cozy could have some kind of fallback logic? Something like:
1) Try to include the bed-symbolic
icon as provided by the user's icon theme
2) If that doesn't exist, load the fallback icon from some file
Then, the icons could be just shipped inside /usr/share/cozy
.
They are released under the Apache 2.0 licence. I believe this is fine for most distros?
Yes, Apache 2.0 is okay. It'd be great if you could add information about the icons and their licences to the README.
Bug/Feature description
When trying to install Cozy Audiobooks from the AUR on EndeavourOS, the build fails with the following error:
I'm not sure what other information you need for my assistance, but please let me know if this could be fixed and I thank you for making a very wonderful app, it has lots of potential. Thank you and have a nice day.
System Information