From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Python Packages
Date: Thu, 30 Jul 2020 08:15:07 +0200 [thread overview]
Message-ID: <ebfc2be3-454d-2ac6-6adb-f05aa3e92a68@gmail.com> (raw)
In-Reply-To: <MN2PR17MB3999C963CE2566A6CFBEBB7EB8710@MN2PR17MB3999.namprd17.prod.outlook.com>
On 30.07.2020 06:57, Allen Hewes via Cygwin wrote:
> Hi,
>
> I have a few Python packages built (and very minor change) for Python 3.8, but before I follow the directions for package contributions, I have a few questions:
>
> 1. I am only running cygport --64 <PYTHON-PACKAGE>.cygport all-test, is there anything else I should do? I have a local "test" repo I use to get them installed via Cygwin Setup.
>
> 2. I am using the --64 arg to cygport because I don't have a 32-bit install of Cygwin, must I get a 32-bit Cygwin install running so I can make 32-bit packages (to be uploaded)?
on 64 bit the --64 is superfluos
You will need a 32 bit installation for the 32bit packages, but most are
"noarch" so you need to build only once
>
> 3. Is there decorum for this of work for Cygwin? Like a packagers mailing list?
cygwin-apps(at)cygwin(dot)com is for packagers
https://cygwin.com/lists.html
>
> 4. Do I or should I have a package mentor? Right now, I am "winging" it b/c my consumer is myself, but I'd like to know how the sausage is made so I Do It Right.
post on that list and we all try to mentor you
>
> The Python packages in the Python 3.8 flavor I have ready:
> python38-asn1crypto
> python38-crypto
> python38-cryptography
> python38-lockfile
> python38-openssl
> python38-pyasn1
> python38-pyasn1-modules
I am currently building from one source for at least 3.6, 3.7 and 3.8
have you looked on the previous source from Yaakov or some of my
last one ?
> Thanks,
>
> /allen
>
next prev parent reply other threads:[~2020-07-30 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 4:57 Allen Hewes
2020-07-30 6:15 ` Marco Atzeri [this message]
2020-07-30 7:25 ` Allen Hewes
2020-07-30 16:59 ` Marco Atzeri
2020-08-12 6:58 ` Marco Atzeri
2020-08-13 14:13 ` Allen Hewes
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=ebfc2be3-454d-2ac6-6adb-f05aa3e92a68@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).