On 8/9/22 7:27 PM, Steven A. Falco wrote:
On 8/9/22 06:42 PM, 'Ian McInerney' via KiCad Developers wrote:


On Tue, Aug 9, 2022 at 8:50 PM Wayne Stambaugh <stambau...@gmail.com <mailto:stambau...@gmail.com>> wrote:

    On 8/9/2022 3:13 PM, Steven A. Falco wrote:
     > On 8/9/22 03:08 PM, Wayne Stambaugh wrote:
     >> Hi Steve,
     >>
     >>
     >> On 8/9/2022 2:37 PM, Steven A. Falco wrote:
     >>> For those who don't follow the Fedora development list, i.e. most
     >>> everyone :-), I've attached two emails related to wxWidgets and
     >>> wxPython.  It looks like we will soon have wxWidgets/wxPython 3.2.0
     >>> in Rawhide.
     >>>
     >>> This change won't apply to the older Fedora releases, so if we want      >>> to keep the nightlies available for Fedora 35 and 36 (and I hope we      >>> can), that will mean that we cannot completely eliminate the older wx
     >>> support from KiCad until F36 goes obsolete, some time around
     >>> mid-2023.  But at least the Rawhide builds can switch soon.
     >>>
     >>> Please let me know if that makes sense, or if there is a need to drop
     >>> wxWidgets/wxPython 3.0 sooner.
     >>
     >> wxWidgets/wxPython 3.2.0 are not even in Debian unstable yet so I
     >> wouldn't worry about dropping 3.0 any time soon.
     >
     > Thanks, Wayne.  I wanted to ask because Ian created an issue asking      > Fedora to switch, so I wasn't sure how hot this was.  I'll add it as it
     > becomes available in the various Fedora releases.
     >
     > https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/issues/43 <https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/issues/43>

    For older versions of KiCad, it might be prudent to stick with what we
    know versus what we don't know.  I know 3.2 resolves some issues but
    it's those unknown issues that I would like to avoid until version 7 is
    released.


The Flatpak has been running the wx 3.1 branch since v6 was released, and so far there have been no issues. We already have Windows and macOS running the 3.1 versions, so I don't see why we need to hold the Linux builds back.

Fair enough but what is the percentage of users using Flatpaks versus native builds? Do we have adequate testing to make this call? I have no idea.


That's good, because there was a wrinkle I was not aware of.  According to the Fedora wx maintainer:

"while wxWidgets versions are parallel installable, wxPython versions are not.  So, once I update to wxPython 4.2.0 (which links with wxWidgets 3.2.0), wxPython 4.0.7 will be gone."

Ughh.  If that is true, then we will have no choice.


I relayed your info to him, and told him to go ahead with wxWidgets 3.2.0 and wxPython 4.2.0, since we cannot hold him up until KiCad 7 becomes available towards the end of the year.  Hopefully there won't be any issues, but if there are I'll yell for help. :-)

     Thanks,
     Steve


--
You received this message because you are subscribed to the Google Groups "KiCad 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to devlist+unsubscr...@kicad.org.
To view this discussion on the web visit 
https://groups.google.com/a/kicad.org/d/msgid/devlist/04c7dd37-3364-2368-3282-119174f8717c%40gmail.com.

Reply via email to