Comment 6 for bug 1629749

Branch with needed changes/fix is available! It was available in same day when Metacity 3.22.0 was released.

"Not sure a port to 3.22 would even still give the ability to read Metacity themes anyway, given the first commit listed above."
How about doing some research before speaking about something you have no idea? Metacity can still use Metacity themes.

"libmetacity: switch from .ssd to .csd"
This commit has nothing to do with Metacity themes. Metacity now supports both - GTK+ themes and also Metacity themes. Your mentioned commit affects only GTK+ theme.

"I haven't spoken with the GNOME people about this, I don't think they would
consider the failure of any non-GNOME package to build against a GNOME
package other than GTK to be a bug, or the report to be a feature request."
I have always updated gtk-window-decorator for all changes I have made to Metacity. Otherwise gdw probably would still use GTK+ 2...

"It would be possible to fork and rename libmetacity 3.20."
Ah, forking, world saver, right?

"To port compiz to 3.22 would not bring back metacity
theme support I'm pretty sure, instead giving support for using the GTK CSD
theme as Metacity itself has done for a couple releases now."
You are so wrong...

"GNOME simply does not use this code anymore and does not even ship metacity themes."
I removed Metacity themes, because:
- metacity by default use GTK+ theme
- all metacity themes was unmaintained