[ITA] python2-wx and related packages for wxPython and wxwidgets
Thu Apr 23 18:52:43 GMT 2020
On Thu, 2020-04-23 at 18:09 +0100, Hamish McIntyre-Bhatty wrote:
> On 23/04/2020 17:08, Yaakov Selkowitz wrote:
> > Please keep all discussion on list.
> My apologies, I thought I'd sent the reply to the list.
> > Most of that has already been figured out in our python-wx package.
> > Looking at Fedora, it looks like we just need to add their wxPython-
> > 18.104.22.168-suppress-version-mismatch-warning.patch and wxPython-22.214.171.124-
> > fix-wxcairo.patch and we'll be in sync.
> Okay, I'll add those patches. I think I've gotten confused somehow,
> because my cygport and files are based on the source package for
> python-wx at
> but the cygport in that archive also builds all of the other packages,
> and doesn't use the system wxWidgets headers, hence me hacking in the
> wxWidgets 3.0.4 files and having to build everything together.
The work to split them out is already published:
I suppose I just never needed to actually rebuild python-wx after that,
but the work was done in preparation.
> wxPython 3.0.2 itself is shipped with wxWidgets 3.0.2 in the tarball
> from wxpython.org, and seems to insist upon building its own copy of
Maybe by default, but it is buildable without.
> > No, that's just bound to cause problems.
> This is confusing me because it seems to be what the existing packages do.
That's what they *used* to do. I moved away from that for the reasons
> > Look forward to the follow up.
> > BTW, did you have any plans to figure out wxPython4?
> Good to hear. I do, I just haven't had the time yet and I figured it'd
> be best to get wxPython 3 in really good shape (and get some practice
> with packaging!) before sorting that one out.
Fair enough. python-sip will need to be updated for that as well,
which requires also updating python-pyqt5* in sync therewith, so this
will need to be coordinated.
More information about the Cygwin-apps