-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
3.22.21: gtk murrine engine dependencies and other gtk 2.x dependent themes #276
Comments
Which distro are you using that doesn't have gtk2-engines-murrine available? |
I'm talking about what is in the git tree. |
Again .. gtk2-engines-murrine is for gtk 2.x which is no longer used by mate components. |
Yep but people may still be using GTK2 apps on distros with MATE as the DE, so the themes still have to support GTK2, and GTK2 themes will generally always rely on some engine package or another. |
Only gtk 2.x application is gimp. |
|
If you will look closet on that list you will find that ~85-90% of that packages are already unmaintained by source tree maintainers. |
So long as any packages distros ship and people USE are using GTK2, we need to support it in our themes. Note that it is often possible to use the pixbuf engine to duplicate theme elements from GTK3, I had to do a lot of such widget screenshotting in my UbuntuStudio_Legacy theme I had to screenshot what Murrine did with menu entries and check/radio buttons and use those in my GTK3 theme, could of course use them in both GTK3 and in GTK2 if murrine ever goes away outright. My guess though is the theme engines and GTK2 go away at the same time, so we need not worry about this |
Looks like some mate-themes themes depends on gtk murrine engine which is no longer available and only supperts gtk 2.x.
I thoing that it would be good to make decision about take over gtk murrine engine mainatainance or remove those themes from source tree as mate desktop compeltly swithed to gtk 3.x.
I'm not sure but I thing that currently there are more gtk 2.x parts.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: