From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: coreutils 9.0 (TEST)
Date: Tue, 19 Jul 2022 13:54:33 -0600 [thread overview]
Message-ID: <72312134-3ac7-e3e5-afc5-a714af7f6d5f@SystematicSw.ab.ca> (raw)
In-Reply-To: <45df4dcc-7bc9-ed66-946e-81d51baf594d@cornell.edu>
On 2022-07-19 12:00, Ken Brown wrote:
> On 7/19/2022 1:07 PM, Brian Inglis wrote:
>> Setup still shows coreutils 9.1 as test, but it should *NOT* be
>> installed by anyone.
>
> Then shouldn't you remove it? And you could also upload an
> override.hint file with a "replace-versions" line for the sake of people
> who have already installed it.
I tried various measures and thought override.hint with
replace-versions: 9.1-1 was there.
How exactly should it be deployed?
Should it be picked up by or specified in cygport?
Within a package, or as a separate file in each directory?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-07-19 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 3:38 Cygwin coreutils Co-Maintainer
2022-07-19 1:50 ` Keith Christian
2022-07-19 2:47 ` René Berber
2022-07-19 11:34 ` Keith Christian
2022-07-19 16:50 ` René Berber
2022-07-19 16:55 ` René Berber
2022-07-31 22:45 ` Keith Christian
2022-07-19 17:07 ` Brian Inglis
2022-07-19 18:00 ` Ken Brown
2022-07-19 19:54 ` Brian Inglis [this message]
2022-07-19 21:06 ` Ken Brown
2022-07-20 3:03 ` Brian Inglis
2022-07-20 4:22 ` Brian Inglis
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=72312134-3ac7-e3e5-afc5-a714af7f6d5f@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).