public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Cygwin x86 end-of-life
Date: Wed, 23 Nov 2022 13:00:02 -0700	[thread overview]
Message-ID: <8880b14f-b404-edb0-16bb-7017b2b9bb79@SystematicSw.ab.ca> (raw)
In-Reply-To: <8735aan1eb.fsf@Rainer.invalid>

On Tue, 22 Nov 2022 22:07:56 +0100, Achim Gratz wrote:
> Brian Inglis writes:
>> As mingw64-i686 target is cross for native Windows 32, and we are
>> dropping Cygwin support for Windows 32, should we not also be dropping
>> cross support for native Windows 32, as so few people are using it,
>> and software developers, packagers, and distros, including us, are
>> dropping it as platform and target?
> 
> I am unlikely to update that toolchain when I move gcc to version 12 or
> later.

So mingw64-i686 cross for native Windows 32 will soon be EoL, and an 
announcement should be made at some point.
That may give us some feedback on whether there is much use of the Cygwin 
packages or whether those available from the Mingw64 project are preferred.

>> Also there are 309 unmaintained mingw64 packages, so perhaps reducing
>> the double (over the base package) extra work of maintaining mingw64
>> packages to a single extra cross might enable us to persuade some
>> maintainers to pick up unmaintained native Windows 64 cross
>> mingw64-x86_64 packages corresponding to the base packages they
>> maintain?
> 
> I can't speak for others, but on my end there's not been much of a
> problem with having the MingW64 packages in two flavors in addition to
> the Cygwin dual architecture builds.  Maybe we'll end up supporting
> ARM64 some way down the road and then it's going to be yet another
> target again for packagers.

A single package build uses all available cpu on my system (0-9% idle), and 
large packages or those with extensive tests take an hour per arch, so it's 4 
hours duration, plus another 3(+/-1) to run on scallywag, sometimes overlapped.
Not usually a problem unless a couple of those upgrade the same week.
Dropping x86 and mingw64-i686 half that.

Once that direction has been determined, perhaps we can suggest here that 
package maintainers pick up related unmaintained mingw64-x86_64 packages, and 
post a list of the suggestions, or a report like the deprecated library and 
unmaintained packages reports linked from the search page.

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

  reply	other threads:[~2022-11-23 20:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 19:30 Brian Inglis
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 [this message]
     [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-15 19:14     ` Erwin Waterlander
2022-11-28 13:08     ` Jon Turney

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=8880b14f-b404-edb0-16bb-7017b2b9bb79@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).