On Sun, 24 May 2026 16:47, Johannes Schauer Marin Rodrigues <[email protected]>
wrote:
Hi,
Quoting Matthias Geiger (2026-05-24 12:51:08)
On Sun, 24 May 2026 08:02, Johannes Schauer Marin Rodrigues <[email protected]>
wrote:
>Hi,
>
>in your last patch for #1079332 you changed in Cargo.toml:
>
>-gtk = { version = "0.8.0", package = "gtk4", features = ["v4_12"] }
>+gtk = { version = "0.9.0", package = "gtk4", features = ["v4_12"] }
>
>and for #1113925 that became:
>
> gtk = { version = "0.10.0", package = "gtk4", features = ["v4_12"] }
>
>Would it not make thing easier in the future if we just change this line to:
>
> gtk = { version = ">= 0.10.0", package = "gtk4", features = ["v4_12"] }
>
unfortunately this is not that easy. gtk-rs usually has breaking changes for
every new release; thus, declaring compatibility with future versions is just
a RC bug waiting to happen. This release has not breaking changes, so it is
as easy as bumping the version in the patch. However, all four previous
releases had major breaking changes.
okay, this is probably why gtk-rs keeps being versioned as 0.x. I'm surprised
nobody finds this super annoying and creates a gtk wrapper for rust *without*
every release breaking all packages that depend on it. Maybe such a wrapper
exists and reform-setup-wizard should switch to such a stable gtk rust binding
instead?
Since this bindings get built against the C sources, which are a moving
target, this is the cause of the frequent breakage.
Upstream at least now only releases once a year; I'd be happy for a
saner solution, however I do not have neither the energy nor the
expertise to change that.
best,
werdahias
