public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
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: Thu, 05 Sep 2019 19:42:00 -0000	[thread overview]
Message-ID: <AM6PR04MB610112C7FB4955C1320F0A11E7BB0@AM6PR04MB6101.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <c4ffa24248863081677d15ad0df676082f32e8ce.camel@cygwin.com>

I thought those were patches that were needed in order to get it to 
build? They didn't seem to apply when I tried them, so maybe I did it 
wrong. Sorry, anyway.

We could have a wxPython 4 build for Python 3 only, and leave the Python 
2 version as it is?

Hamish

On 05/09/2019 20:35, Yaakov Selkowitz wrote:
> On Thu, 2019-09-05 at 16:36 +0000, Hamish MB wrote:
>> Attached is a patch from git format-patch to upgrade the wxwxidgets
>> version to 3.0.4.
> Obviously, I'm not going to accept this patch as is, since it removes
> all the modifications I have made to the package.  However, I did go
> ahead and update to 3.0.4, which is now working its way to mirrors.
>
>> Next up I'll try to make a package for wxPython 4, but I have to get
>> it to build first.
> Since this would conflict with the existing python-wx package, either
> this needs to be a compatible replacement for 3.0, or the packaging
> needs to be modified to be parallel-installable.
>
> --
> Yaakov
>
>

  reply	other threads:[~2019-09-05 19:42 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 [this message]
2019-09-05 21:19     ` Yaakov Selkowitz
2019-09-06  8:58       ` Hamish MB
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=AM6PR04MB610112C7FB4955C1320F0A11E7BB0@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).