From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin-apps@cygwin.com>
Subject: RE: Cygwin x86 end-of-life
Date: Mon, 14 Nov 2022 16:29:34 -0500 [thread overview]
Message-ID: <0e6b01d8f870$314b1760$93e14620$@pdinc.us> (raw)
In-Reply-To: <073da66f-41fe-a46a-3f79-047cdf096f3d@SystematicSw.ab.ca>
> -----Original Message-----
> From: Brian Inglis
> Sent: Monday, November 14, 2022 3:17 PM
>
> On Mon, 14 Nov 2022 16:25:18 +0000, Jon Turney wrote:> On 11/11/2022 16:16, Jon
> Turney wrote:
> >> On 11/11/2022 15:50, Jon Turney wrote:
> >>> As has previously been announced, Cygwin is dropping support for x86
> >>> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit)
> >>> Windows, and the forthcoming Cygwin 3.4 will be released for x86_64 only.
> >>>
> >>> Concurrent with that, updates to x86 packages will be stopped, and the
> >>> Cygwin x86 package repository will be archived.
>
> >> I plan to pause package uploads this coming Monday (2022-11-14), before
> >> starting the re-organization of the package repository to make this
> >> archive.
>
> > Since there have been some complaints about short notice, and to give
> > time to work out the issues with gettext/libunistring, I'm going to
> > defer this by one week, until Monday 2022-11-21.
>
> Thank you very much appreciated, hopefully we can deal with the remaining issues
> quickly.
I do not have an articulate retort to ending support, but all I can say is that I feel there must be a middle ground.
I feel that there could and should be some form of "we don’t support it" but we are not going out of our way to prevent it.
Can I throw resources at a solution? If so what?
Feel free to ignore my grumpy ramblings.
-Jason
--
Jason Pyeron | Architect
PD Inc | Certified SBA 8(a)
10 w 24th St | Certified SBA HUBZone
Baltimore, MD | CAGE Code: 1WVR6
.com: jpyeron@pdinc.us
tel : 202-741-9397
next prev parent reply other threads:[~2022-11-14 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cfc30991-0dd0-3308-9aca-df7cf81169aa@dronecode.org.uk>
2022-11-11 16:16 ` Jon Turney
2022-11-11 19:45 ` Thomas Wolff
2022-11-11 19:50 ` Achim Gratz
2022-11-11 20:02 ` Thomas Wolff
2022-11-12 16:08 ` Jon Turney
2022-11-12 16:58 ` Thomas Wolff
2022-11-13 13:58 ` Thomas Wolff
2022-11-13 16:43 ` Achim Gratz
2022-11-13 17:01 ` Thomas Wolff
2022-11-13 17:07 ` Jon Turney
2022-11-13 19:17 ` Corinna Vinschen
2022-11-14 15:24 ` Andrew Schulman
2022-11-13 20:31 ` Brian Inglis
2022-11-14 16:25 ` Jon Turney
2022-11-14 17:18 ` Andrew Schulman
2022-11-14 20:16 ` Brian Inglis
2022-11-14 21:29 ` Jason Pyeron [this message]
2022-11-18 15:51 ` Jon Turney
2022-11-15 19:14 ` Erwin Waterlander
2022-11-28 13:08 ` Jon Turney
2022-11-21 12:45 Corinna Vinschen
2022-11-22 17:51 ` Brian Inglis
2022-11-22 21:07 ` Achim Gratz
2022-11-23 20:00 ` 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='0e6b01d8f870$314b1760$93e14620$@pdinc.us' \
--to=jpyeron@pdinc.us \
--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).