public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python-getdevinfo
Date: Fri, 4 Sep 2020 14:38:57 +0100	[thread overview]
Message-ID: <DB7PR02MB3996994085EFCA424E1E937CE72D0@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <3e539041-57fd-6356-1afd-b8c86941a2b9@cornell.edu>


[-- Attachment #1.1.1: Type: text/plain, Size: 951 bytes --]

On 03/09/2020 19:50, Ken Brown via Cygwin-apps wrote:
> On 9/3/2020 1:27 PM, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 03/09/2020 18:13, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>> <cut>
>>> Good to know, and oh yeah, I'll do that tomorrow.
>>>
>>> Cheers for the vote.
>>>
>>> Hamish
>>>
>> I should note that this is a pure python package - can it be a noarch
>> package? I'm not sure how to configure the cygport file to build a
>> noarch package.
>
> Just put the line
>
>   ARCH=noarch
>
> in the cygport file.
>
> Ken

Thank you, that seemed to work well.

New build dependencies added (also util-linux, binutils, cygwin, and
coreutils), and updated as a noarch package with no other changes. The
new files are in the "noarch" subdirectory at
https://www.hamishmb.com/files/cygwin-temp/.

I gave the noarch packages I built on 64-bit Cygwin a spin on 32-bit
Cygwin too, all seems fine.

Hamish


[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-04 13:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 13:33 Hamish McIntyre-Bhatty
2020-08-17 13:34 ` Hamish McIntyre-Bhatty
2020-08-19  5:53   ` Marco Atzeri
2020-08-19 11:22     ` Hamish McIntyre-Bhatty
2020-08-20  6:01       ` Marco Atzeri
2020-08-21 15:33         ` Hamish McIntyre-Bhatty
2020-08-26  9:35           ` Hamish McIntyre-Bhatty
2020-09-02 15:29             ` Hamish McIntyre-Bhatty
2020-09-02 18:05               ` Marco Atzeri
2020-09-02 20:58                 ` Hamish McIntyre-Bhatty
2020-09-03 13:44                   ` marco atzeri
2020-09-03 14:10                     ` Hamish McIntyre-Bhatty
2020-09-03 16:34                       ` Ken Brown
2020-09-03 17:13                         ` Hamish McIntyre-Bhatty
2020-09-03 17:27                           ` Hamish McIntyre-Bhatty
2020-09-03 18:50                             ` Ken Brown
2020-09-04 13:38                               ` Hamish McIntyre-Bhatty [this message]
2020-09-09 10:36                                 ` Hamish McIntyre-Bhatty
2020-09-12 22:19                                   ` Hamish McIntyre-Bhatty
2020-09-13  6:13                                     ` Achim Gratz
2020-09-13  7:39                                       ` Hamish McIntyre-Bhatty
2020-09-13 15:02                                         ` Brian Inglis
2020-09-13 16:08                                           ` Hamish McIntyre-Bhatty
2020-09-14 18:29                                             ` Hamish McIntyre-Bhatty
2020-09-13 14:57                     ` Jon Turney
2020-09-13 16:07                       ` Hamish McIntyre-Bhatty
2020-09-22 13:32                         ` 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=DB7PR02MB3996994085EFCA424E1E937CE72D0@DB7PR02MB3996.eurprd02.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).