https://bugzilla.redhat.com/show_bug.cgi?id=2141725
--- Comment #4 from Kalev Lember klember@redhat.com --- Thanks for the review, Fabio! I really appreciate all the help here.
(In reply to Fabio Valentini from comment #3)
Please don't waste your time on trying to update the gtk-rs stack to v0.16 / gtk4-rs v0.5 / gstreamer-rs v0.19, as that's probably above your pay grade (yes, it's not lost on me that I don't get paid for this stuff at all).
I don't understand at all what you mean with the pay grade comment. Can you clarify, please?
The glib / gtk3 / gtk4 / gstreamer bindings are a tangled mess that can only be updated as a single unit. They're also one of the few groups of Rust packages that are only ever updated in rawhide, because they break so many things with each "major" update (gtk-rs 0.15 -> 0.16, in this case), and gtk-rs applications we ship often need some time to adapt to the new versions.
I will handle the gtk-rs v0.16 + gtk4-rs v0.5 + gstreamer-rs v0.19 mega-update in F38 once things have settled down, but for now, we'll have to stick with gtk-rs v0.15 + gtk4-rs v0.4 + gstreamer-rs v0.18.
I think it's worth trying to make sure there are more than one people who know enough to keep the stack updated. If you don't mind, I'd like to be involved in updating it this time around.
What makes it especially complicated? Is there something in the stack that makes it hard to do compat packages to keep apps that haven't been updated for the new version working?
If it's so hard to keep it up to date, maybe we should suggest vendoring it all instead...
===
You can add this rust2rpm.conf file to automate adding Build/Requires:
[DEFAULT] buildrequires = pkgconfig(libadwaita-1) >= 1.0.0 lib.requires = pkgconfig(libadwaita-1) >= 1.0.0
Yes, thanks -- I already had that.