On Sun, Aug 11, 2013 at 10:17:48PM +0200, Sebastian Reichel wrote:
> What's the status of your packaging? wxWidgets 2.9.5 has been
> released roughly a month ago. I would like to update aegisub to 3.x
> branch, since 2.x branch is no longer maintained by upstream
> maintainers.
I've been on vacation, and then my wx packaging energies were taken with
sorting out wx 2.8 bugs which were reported while I was away.
Hopefully I should be on to 2.9 soon though.
> ABI bumps in libwxWidgets would mainly be a problem for reverse
> dependencies. From my perspective (maintainer of a reverse
> depdendency) multiple ABI bumps in wxWidgets are the lesser evil
> compared to being totally unsupported by upstream developers.
wx 2.8 isn't totally unsupported upstream. It's true that there haven't
been any wx 2.8 releases for ages, but there are still commits to the
branch - last was 18 days ago as I write this:
https://github.com/wxWidgets/wxWidgets/commits/WX_2_8_BRANCH
> Please note, that having software with an unstable API in Debian is
> not that uncommon (enlightenment [by now stable], libfso*,
> libradare*, ...). It obviously increases the maintenance work,
> though.
The increased maintenance work is a real issue. I'm the only active
member of the wx maintenance team at the moment, with limited time to
devote to it, and wx has a lot of reverse dependencies (many without an
active maintainer judging from the number of NMUs I had to do to get rid
of wx 2.6).
Cheers,
Olly
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130904013245.gr31...@survex.com
