public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Jason Pyeron <jpyeron@pdinc.us>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: RE: Cygwin x86 end-of-life
Date: Fri, 18 Nov 2022 15:51:34 +0000	[thread overview]
Message-ID: <378b9150-65f2-b987-d8f1-f6cf8c2900c2@dronecode.org.uk> (raw)
In-Reply-To: <0e6b01d8f870$314b1760$93e14620$@pdinc.us>

On 14/11/2022 21:29, Jason Pyeron wrote:
>> -----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.

I'm unclear if this means:

(a) "releasing Cygwin 3.4.x DLL for x86 OS"
(b) "don't require x86 uploads, but don't prevent them, either"

The problem I have with (b) is that we probably end up in a state where 
x86 is missing package updates people want or need; or broken, but we 
don't know it, because nobody uses it.

> Can I throw resources at a solution? If so what?

Sure, if that's what you want to do.

According surveys, 32-bit Windows has a fraction of 1% market share, and 
declining. Our own (limited) metrics are in accord with that, so I 
basically see any time I spend on this as wasted.

So, the first resource you'll need provide is manpower.


  reply	other threads:[~2022-11-18 15:51 UTC|newest]

Thread overview: 23+ 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
2022-11-18 15:51         ` Jon Turney [this message]
2022-11-15 19:14     ` Erwin Waterlander
2022-11-28 13:08     ` Jon Turney
2022-11-18 19:30 Brian Inglis
2022-11-21 12:45 ` Corinna Vinschen
2022-11-22 17:51   ` 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=378b9150-65f2-b987-d8f1-f6cf8c2900c2@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=jpyeron@pdinc.us \
    /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).