Re: Proposed MBF: wxwidgets3.2 transition
On Tue, 13 Sep 2022, Mattia Rizzolo wrote:
On Mon, Sep 12, 2022 at 10:32:23PM -0400, Scott Talbert wrote:
wxWidgets 3.2 (a new API/ABI stable release) has been released a few months
ago and is now packaged in unstable as wxwidgets3.2. Upstream has stopped
supporting wxWidgets 3.0, so the Debian wx team would like to migrate all wx
package users to wxwidgets3.2 for bullseye, with the plan to remove
wxwidgets3.0 before release.
For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some packages
may require small patches; I'm happy to help with those (and I have some
already from working on this transition in Fedora already).
Question from somebody who doesn't know wxWidgets: if the update from
one release to the other is so simple (at least, you make it sound very
simple, and #1019416 has no blocking bugs, so I reckon everything
works?) then why is this not packaged like pretty much any other library
with an unversionde source package and an unversioned -dev binary
Major wxWidgets releases are not API compatible, so there will be packages
that will require changes (although there are not many
backwards-incompatible API changes between 3.0 and 3.2). I would think of
it more akin to GTK-2 vs GTK-3, although there are not as many API
changes. Historically, there have been larger API changes between
releases (e.g., 2.8 to 3.0).
I suppose it would be technically possible to do it with a single -dev
package, but that would lead to potentially extended breakages of unstable
while the packages that require changes get updated.