Arch Linux User Repository

There hasn't been any new tagged release version since 2019, but there is a treesheets-git, which is supposed to work with current libraries.

Well I realised this pushes back the problem to another dependency (libtiff5 which is apparently built with ABI 1017 by default). Maybe it's time to retire this package.

I looked at creating a -bin and decided I do not want to replicate the entire Debian dependency tree just for one package. Anyway, dependency is updated now. I'm guessing @MarsSeed you've already requested to delete wxgtk30?

Considering this is a -bin package, I will probably go the route of creating a -bin dependency as well with appropriate provides. Then we can see if the other maintainer adds the provides to their package, and then users can choose either option.

@eclairevoyant sorry for flagging this, you are absolutely right.

For practical reasons, I recommend to use wxwidgets3.0 for now. If only because it has the correct ABI version.

Ideally, yes, that should be a split package. But it's typically not easy and quick to convince package maintainers to make these kinds of changes.

Though in actuality, even a unified wxwidgets3.0 package could provide all the other wxwidgets bindings (gtk2, gtk3, qt), if it was built so, and if it declared the needed provides elements.

Unfortunately the current maintainer doesn't even want to add the virtual provides, together with the relevant versions, for the same elements that repo's wxwidgets-gtk3 package declares.

So looking at the AUR, there are all these packages doing approximately the same thing, and none of them follow the naming scheme of the package in the repos:

pkgbase = wxwidgets, and pkgname = (wxwidgets-gtk3, wxwidgets-qt5, wxwidgets-common)

Shouldn't wxwidgets3.0 be changed first before I start messing with dependencies? This would then depend on something the split package wxwidgets3.0-gtk3.

BTW for non-VCS packages, flagging OOD only applies if there is a new version released or something, it's not for reporting bugs nor for making requests. If you have an issue just comment.

I recommend that you make this package depend on wxwidgets3.0.

That one is built with the required -fabi-version=13 flag.

Thanks for adopting this package, @eclairevoyant!

Adopted and updated. Keep in mind that if you use wxgtk30 it must be compiled against C++ ABI 1013, which requires adding something like this to the build() function of wxgtk30's PKGBUILD:

export CXXFLAGS="$CXXFLAGS -fabi-version=13"

Alternatively I'll see if I can make a wxgtk30-bin this week.