public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Allen Hewes <allen@decisiv.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Python Packages
Date: Thu, 30 Jul 2020 04:57:02 +0000	[thread overview]
Message-ID: <MN2PR17MB3999C963CE2566A6CFBEBB7EB8710@MN2PR17MB3999.namprd17.prod.outlook.com> (raw)

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)?

3. Is there decorum for this of work for Cygwin? Like a packagers mailing list?

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.

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

Thanks,

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

             reply	other threads:[~2020-07-30  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  4:57 Allen Hewes [this message]
2020-07-30  6:15 ` Marco Atzeri
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=MN2PR17MB3999C963CE2566A6CFBEBB7EB8710@MN2PR17MB3999.namprd17.prod.outlook.com \
    --to=allen@decisiv.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).