From: Hamish MB <hamishmb@live.co.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Updated cygport for for wxwidgets 3.0 package
Date: Fri, 06 Sep 2019 08:58:00 -0000 [thread overview]
Message-ID: <AM6PR04MB61014FBB5206A8CEE2A1B424E7BA0@AM6PR04MB6101.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <a640906445b130f62d4d2254d95a23ec26b2d80d.camel@cygwin.com>
On 05/09/2019 22:19, Yaakov Selkowitz wrote:
> Patches have been written, or applied from other sources, for any
> number of reasons. It would be wise to attempt to understand why.
Yes. I'm now rebuilding using your updated cygport file and examining
the patches in order to better understand how it works. I think I must
have gotten confused - I think it was the wxpython patches that can't be
applied any more because the codebase has changed a lot, but I'll
investigate that further. I did hear that some of the patches come from
Gentoo, is that right? As you can tell, I'm very new to using patches
and packaging for Cygwin, and I apologise for my newbie questions.
>> We could have a wxPython 4 build for Python 3 only, and leave the Python
>> 2 version as it is?
> I'd be willing to consider that.
Great, when I get it working, I'll see if I can get the existing patches
to apply and then go from there.
Hamish
next prev parent reply other threads:[~2019-09-06 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 16:37 Hamish MB
2019-09-05 19:35 ` Yaakov Selkowitz
2019-09-05 19:42 ` Hamish MB
2019-09-05 21:19 ` Yaakov Selkowitz
2019-09-06 8:58 ` Hamish MB [this message]
2019-09-07 15:08 ` Jon Turney
2019-09-07 18:48 ` Hamish MB
2019-09-07 19:12 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM6PR04MB61014FBB5206A8CEE2A1B424E7BA0@AM6PR04MB6101.eurprd04.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).