https://wxwidgets.org/news/2016/02/wxwidgets-3.1.0-released/
wxGTK-3.1.0 is a first development release leading up to stable 3.2 series. I'm not sure we'd want to add it unless we need it for some reason in p.mask or something (maybe as a convenience for devs using wx or something). But up to Ryan I think.
I think we'll only be adding 3.1 if a package explicitly needs it.
*** Bug 591260 has been marked as a duplicate of this bug. ***
(In reply to Ryan Hill from comment #2) > I think we'll only be adding 3.1 if a package explicitly needs it. Apparently games-emulation/dolphin.
wxGTK 3.1.0 includes a fix for bug 592436. At the moment, 3.0 fails to build with GCC 6. See that thread as well, thanks.
(In reply to Ryan Hill from comment #2) > I think we'll only be adding 3.1 if a package explicitly needs it. Any application that allows binding of custom keys for accelerator functions, can use multimedia keys only in 3.1. Eg media-sound/guayadeque
Created attachment 464828 [details] wxGTK-3.1.0.ebuild This is my attempt of an ebuild for wxGTK 3.1.0, based on wxGTK-3.0.2.0-r301.ebuild The differences are : - The source URI is now on GitHub - The archive is wxWidgets-${PV}.tar.bz2 instead of wxPython-src-${PV}.tar.bz2 - I removed the docs archive, as I didn't know how to handle it - I didn't use any patch - I removed some references to 3.0 in the body of functions and put them in the header as variables, like ${WXVERSIONTAG} and ${WXRELEASE_NODOTSLASH} (this one is new) I needed this version for another ebuild that is not in the portage tree, but in Bug 376187
http://wxwidgets.org/news/2018/02/wxwidgets-3.1.1-released/
The ebuild I proposed for 3.1.0 also worked for 3.1.1 on my system, simply by renaming it to the new version number.
there is a small change necessary to proceed wrt the proto packages : the changed part is : X? ( x11-base/xorg-proto[${MULTILIB_USEDEP}] )" I'm currently trying to build this, but this is a bit confusing : The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by wxGTK:3.1-gtk3 (argument) >=x11-libs/wxGTK-3.1.0 -abi_x86_32 Any hints?
x11-libs/wxGTK-3.1.1-r301 and a modified wxwidgets.eclass are available in my overlay: https://github.com/stefantalpalaru/gentoo-overlay
Current cubicsdr requires at least 3.1.1, and the old release in ::gentoo fails to produce any audio output. It is sad the pull request was not applied.
Bump.
3.1.x is still a development release whose ABI will be different compared to another 3.1.x release. Nothing has changed in this regard. If an application requires a development version, then the overall result can't be considered stable and it's arguable it belongs in the main tree.
(In reply to Mart Raudsepp from comment #14) > 3.1.x is still a development release whose ABI will be different compared to > another 3.1.x release. Nothing has changed in this regard. If an application > requires a development version, then the overall result can't be considered > stable and it's arguable it belongs in the main tree. Why not make it a slotted package or stage it in ~*, then?
~arch can be considered stable candidate. wxGTK-3.1.x will never be a stable candidate. There is no manpower right now to maintain this in package.mask for the time being. You are free to take your complaints to upstream for not releasing new feature releases in a sensible release timeline.
https://github.com/perfect7gentleman/pg_overlay/blob/master/x11-libs/wxGTK/wxGTK-3.1.2-r300.ebuild
wxWidgets 3.1.3 Released Posted on October 28, 2019 Please notice that while 3.1.3 is officially a “development” version because it is not fully compatible with the “stable” 3.0.x, the list of backwards incompatible changes is very short, so you shouldn’t have any problems updating to this version from 3.0.x in practice, and you’re encouraged to use this release, including in production.
wxGTK-3.1.3-r300 available in my overlay: https://github.com/stefantalpalaru/gentoo-overlay Tested with cubicsdr-0.2.5_p20191029
Tested (and works) with dev-util/codelite-9999 in my local overlay.
(In reply to Frank Krömmelbein from comment #18) > wxWidgets 3.1.3 Released > Posted on October 28, 2019 > > Please notice that while 3.1.3 is officially a “development” version because > it is not fully compatible with the “stable” 3.0.x, the list of backwards > incompatible changes is very short, so you shouldn’t have any problems > updating to this version from 3.0.x in practice, and you’re encouraged to > use this release, including in production. And there are no guarantees a 3.1.4 will be ABI compatible with this 3.1.3. This is far from production ready in linux distributions. They mainly have in mind using it "in production" when static linking to the wx library in windows and Mac builds, and self-made semi-proprietary linux builds that ship with wx itself.
From the official webpage at https://www.wxwidgets.org/: > wxWidgets 3.1.3 Released > > Posted on October 28, 2019 > > wxWidgets 3.1.3 release is now available on GitHub. [...] > > Please notice that while 3.1.3 is officially a “development” > version because it is not fully compatible with the “stable” > 3.0.x, the list of backwards incompatible changes is very > short, so you shouldn’t have any problems updating to this > version from 3.0.x in practice, and you’re encouraged to > use this release, including in production. A few packages that could be maintained in portage require the 3.1 API, such as freefilesync, for example. This should be available as ~arch at least, as per the upstream statement about it being production-ready. As there have been some portage-specific patches in the 3.0.4 ebuilds, it would be nice if one of the experts on wxGtk on Gentoo would provide at least an ebuild to locally overlay the wxGtk 3.1.3 version in a slot, as an attachment here, if you're still uncomfortable about having it in the official repository. It's unclear which patches out of https://dev.gentoo.org/~leio/distfiles/wxGTK-3.0.4_p20190713.tar.xz are code-related and/or any of them are Gentoo or Portage-specific, so others can pick up from there. I hate to be a nag, but if upstream encourages to use 3.1, then there will be more and more packages actually requiring it. Could there be changes in 3.1.4? Maybe, maybe not. That'll be in upstream's hand, and developers of 3.1-dependent packages will have to deal with it, and recompile, or maintainers of such packages on Gentoo might need a patch here and there. But last time I looked, that's what Gentoo was made for, and why I use and like it. If I wanted outdated binary packages, I'd run Ubunto LTS...
You should direct your nag energy to wxWidgets upstream about releasing a stable feature version then :) If they say it's stable and ABI won't change, then they should release 3.2.0, not wait another year until someone finally decides the remaining new API and features no-one is working on don't need to go into that 3.2 release. We are not Windows, for which they encourage to static link some random development version in there, as ABI stability isn't of concern with static linkage.
Well, it would at least be nice to have an update to wxWidgets 3.0.5, the latest release in the stable 3.0 series. (came out in April this year) However, I'll test whether I can fix #650500 with an update to 3.0.5 or 3.1.4 (will try both), as that bug pesters me for years now.
https://trac.wxwidgets.org/wiki/Roadmap "Development branch and 3.2 New development happens on 3.1 branch. The latest version is 3.1.4, released on July 22, 2020 and we plan to release one last 3.1.5 release in 3.1.x series in the beginning of 2021 with 3.2.0 hopefully following soon after. One of the big planned changes for this 3.2 is better support for high DPI displays, but there are, of course, many, many other fixes and improvements in it as well. 3.2 will also finally drop support for very old legacy systems (such as Win9x platform) and compilers (MSVC6, maybe MSVC7 as well)."
https://trac.wxwidgets.org/wiki/Roadmap "New development happens on 3.1 branch. The latest version is 3.1.5, released on April 14, 2021 and we plan to release one last 3.1.6 release in 3.1.x series in a couple of months with 3.2.0 hopefully following around September 2021."
