From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) by sourceware.org (Postfix) with ESMTP id 4E991385DC0B for ; Thu, 23 Apr 2020 16:08:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4E991385DC0B Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=yselkowitz@cygwin.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-457-nG7KpSrtNLiJnaXwXup30A-1; Thu, 23 Apr 2020 12:08:40 -0400 X-MC-Unique: nG7KpSrtNLiJnaXwXup30A-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EEBAB100AA23 for ; Thu, 23 Apr 2020 16:08:19 +0000 (UTC) Received: from ovpn-117-23.rdu2.redhat.com (ovpn-117-23.rdu2.redhat.com [10.10.117.23]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9B9076084C for ; Thu, 23 Apr 2020 16:08:19 +0000 (UTC) Message-ID: <4e18c5fb1716a1e3e44b0e0d5591eeec517cd603.camel@cygwin.com> Subject: Re: [ITA] python2-wx and related packages for wxPython and wxwidgets From: Yaakov Selkowitz To: cygwin-apps@cygwin.com Date: Thu, 23 Apr 2020 12:08:18 -0400 In-Reply-To: References: <5e22328970c8702c69d1f2c83e3de3b89ad908e8.camel@cygwin.com> User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-8.2 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2020 16:08:43 -0000 On Thu, 2020-04-23 at 16:16 +0100, Hamish McIntyre-Bhatty wrote: > Thanks for your feedback. I wasn't expecting this to be accepted, it's > only my first try after all :) Please keep all discussion on list. > > I do not recommend building both the C++ libraries and Python bindings > > from the same source package, for several reasons: > >=20 > > * Python bindings need to be updated/rebuilt with each new version of > > Python, which occurs much more frequently than updated versions of > > wxWidgets. Keeping them separate minimizes the rebuild times. > >=20 > > * wxPython and wxWidgets versions don't always match, as you mentioned > > above. Building them separately avoids jumping through those sort of > > hoops. > >=20 > > * wxPython 3 is obsolete anyway, with current support only for version > > 4 (which is still for wxWidgets 3), so this scheme won't carry forward > > anyway. > >=20 > > Since the standalone wxWidgets3.0 package is already at 3.0.4, all you > > may want to do is revbump and rebuild python-wx. >=20 > This is fair enough. However, I was unable to build wxPython against the > already-installed system version of wxWidgets, as that isn't how it was > intended to be compiled, and it would require large changes to the > pre-existing packaging. Most of that has already been figured out in our python-wx package.=20 Looking at Fedora, it looks like we just need to add their wxPython- 3.0.2.0-suppress-version-mismatch-warning.patch and wxPython-3.0.2.0- fix-wxcairo.patch and we'll be in sync. > How about I instead ignore the wxwidgets packages built this way? This > will result in long build times as per the pre-existing packaging, but > there will probably not be much need to re-build this. No, that's just bound to cause problems. > > Do NOT drop this patch. You might be aligned now, but as soon as > > gcc/libstdc++ get updated, the mismatch will reoccur, and programs will > > unnecessarily fail again. > Okay, I shall re-instate it and re-build. > > > The few remaining wxGTK* patches: > > > - No longer apply without error and don't seem to be needed with the > > > newer wxwidgets version. > > Patches were added for a reason; if you don't understand what they do > > and why they're there, then you should be asking why rather than > > dismissing them. In the case of Gentoo's collision patch, this is > > needed to support parallel installations of X.Y versions of wxWidgets.= =20 > > The updated patch is named wxGTK-3.0.5-collision.patch. > >=20 > Good to know, I will attempt to find updated patches. Is there an online > repository where they are held? I will go back through the other patches > which did not apply and attempt to find replacements/ask what they do. Look forward to the follow up. BTW, did you have any plans to figure out wxPython4? -- Yaakov