From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/3] CI update
Date: Fri, 28 Aug 2020 07:57:24 -0600 [thread overview]
Message-ID: <2abf7aa2-c926-8f7b-3f70-b508b33fe101@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200828084305.GH3272@calimero.vinschen.de>
On 2020-08-28 02:43, Corinna Vinschen wrote:
> On Aug 27 13:29, Brian Inglis wrote:
>> On 2020-08-27 02:49, Corinna Vinschen wrote:
>>> On Aug 26 22:04, Jon Turney wrote:
>>>> Since we recently had the unpleasant surprise of discovering that Cygwin
>>>> doesn't build on F32 when trying to make a release, this adds some CI to
>>>> test that.
>>>>
>>>> Open issues: Since there don't seem to be RedHat packages for cocom, this
>>>> grabs a cocom package from some random 3rd party I found on the internet.
>>
>> New official site V0.98 Unicode 8:
>>
>> https://github.com/dino-lang/dino/blob/master/cocom.spec
>
> Weird version numbering scheme. Our cocom package is version 0.996.
> Is it safe to assume this stuff is newer then ours?
Same guy Vladimir Makarov and link from previous SF to current GH sources; not
seeing the earlier emphasis on Russian armaments, rather focus is on Dino
language; affiliation RedHat Toronto; GH INSTALL files all date from 20 years
ago; our CHANGES says Win32 support was removed in 2007 at the top, and that
agrees with GH ChangeLog, which continues up to 2019; closed Issue mentions he
changed to autotools for Cygwin and MacOSX between 2015 and 2016; switches email
from users.sf.net to gcc.gnu.org in 2016, and redhat.com briefly 2016 Mar, about
when he switched to GH.
There are few mentions of versions; preference on GH seems to be dates, latest
mainly 2016, regenerated configure, Makefile.in, aclocal.m4 across directories 9
months ago: although our file dates are 2015, that version 0.996 applies to
Ammunition from 2002; version mentions include above Ammunition v0.996,
Onigurama 6.0.0, Dino updates to .5 and .55, http://dino-lang.github.io/download
offers V0.97 with Dino 0.5, GH says V0.98 with Dino 0.55.
--
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 IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-08-28 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 21:04 Jon Turney
2020-08-26 21:04 ` [PATCH 1/3] Cygwin: Add .appveyor.yml Jon Turney
2020-08-26 21:04 ` [PATCH 2/3] Cygwin: Add github action to cross-build on Fedora Jon Turney
2020-08-26 21:04 ` [PATCH 3/3] Cygwin: Remove .drone.yml Jon Turney
2020-08-27 8:49 ` [PATCH 0/3] CI update Corinna Vinschen
2020-08-27 19:29 ` Brian Inglis
2020-08-28 8:43 ` Corinna Vinschen
2020-08-28 13:57 ` Brian Inglis [this message]
2020-08-28 13:24 ` Corinna Vinschen
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=2abf7aa2-c926-8f7b-3f70-b508b33fe101@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@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).