From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python36-wx 4.0.7.post2
Date: Tue, 9 Jun 2020 21:53:47 +0200 [thread overview]
Message-ID: <2b10fc1f-26e0-6507-2c2c-7330d1dd4f6d@gmail.com> (raw)
In-Reply-To: <AM0PR05MB4898204103D5C3575C6B62C8E7820@AM0PR05MB4898.eurprd05.prod.outlook.com>
On 09.06.2020 18:52, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Hello,
>
> Sending this email to say that I intend to package python36-wx
> 4.0.7.post2 (wxPython 4.0.7.post2 compiled for Python 3.6). My test
> packages are available at https://www.hamishmb.com/files/cygwin-temp/
>
> I wasn't sure which Python 3 version to build against, but it seems most
> packages are built against 3.6. I will happily build for 3.7 and 3.8 as
> well if needed.
>
> One thing I'm not sure of is that in order to avoid conflicts with
> python-wx (wxPython 3 for Python 2), I have to rename some of the
> binaries that are installed in /usr/bin - see the cygport file for details.
>
> If anyone has any feedback I'd appreciate it very much.
>
> Hamish McIntyre-Bhatty
>
It is probably possible to build
python36-wx and python37-wx together with the same source package.
The only files of the binaries they seem to share are
usr/share/icons/hicolor/16x16/apps/PyCrust.png
usr/share/icons/hicolor/32x32/apps/PyCrust.png
that can be put in a tiny shared common subpackage
python38-wx will need python38-numpy that is not yet available.
Maybe it is also possible to build python27-wx, but I doubt is is worth
the effort as we should move faster on python3.8
Questions:
- why 4.0.7.post2 and not 4.1.0 ?
- have you a BUILD_REQUIRES list ?
just to avoid a try loop to test my idea
Regards
Marco
next prev parent reply other threads:[~2020-06-09 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:52 Hamish McIntyre-Bhatty
2020-06-09 19:53 ` Marco Atzeri [this message]
2020-06-10 9:34 ` Hamish McIntyre-Bhatty
2020-06-11 15:19 ` Marco Atzeri
2020-06-11 16:03 ` Hamish McIntyre-Bhatty
2020-06-11 16:41 ` Marco Atzeri
2020-06-15 10:20 ` Hamish McIntyre-Bhatty
2020-06-15 18:26 ` Achim Gratz
2020-06-17 8:41 ` Hamish McIntyre-Bhatty
2020-06-17 19:24 ` Marco Atzeri
2020-06-17 21:23 ` Hamish McIntyre-Bhatty
2020-06-18 8:20 ` Hamish McIntyre-Bhatty
2020-06-18 9:24 ` Marco Atzeri
2020-06-18 11:31 ` Hamish McIntyre-Bhatty
2020-06-18 14:08 ` Jon Turney
2020-06-18 15:05 ` Hamish McIntyre-Bhatty
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=2b10fc1f-26e0-6507-2c2c-7330d1dd4f6d@gmail.com \
--to=marco.atzeri@gmail.com \
--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).