public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Last Version of Cygwin for XP
Date: Fri, 12 Feb 2016 19:20:00 -0000	[thread overview]
Message-ID: <4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com> (raw)
In-Reply-To: <56BCCE7D.6040605@gmail.com>

On Feb 11, 2016, at 11:10 AM, cyg Simple <cygsimple@gmail.com> wrote:
> 
> A git tag would be helpful for LAST-XP supported version.

Easy to do, but I wonder how many people would use it?  I doubt there’s a lot of overlap between the group of people unwilling to upgrade their XP boxes and the group willing to install development tools, clone git repos, backport patches from trunk, and build local DLLs.

If there were a large overlap, Red Hat wouldn’t be raking in billions supporting 10-year-old Linux boxes.

That begs a question: Is there a market for a “Cygwin LTS” service, where someone does all that backporting for a tiny recalcitrant minority of Windows XP + Cygwin users?  Who knows, maybe there’s a new line of revenue there for Red Hat. :)

> There are certainly plenty of XP still being used that takes advantage of Cygwin.

I hope not.  Extended support ended nearly two years ago.  That’s 22 months of unfixed security problems, bugs, and regressions with respect to the state of the world.  (By the latter, I mean things like outdated time zone rules.)

The last time this topic came up, I came away with the impression that the only reason Cygwin hasn’t jettisoned XP support yet is that it’s more work than ignoring that old code.

Eventually, Cygwin’s gonna have to scrape that barnacle off the hull.  You should already have your Cygwin XP install trees packed up in anticipation of that day.

> The problem will be the other packages that stop support of older
> Cygwin versions.

That’s why you archive your installation tree.

And for those without that foresight and preparedness, there’s the Cygwin Time Machine.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-02-12 19:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  1:37 Jonathan Brenster
2016-02-10  2:17 ` Yaakov Selkowitz
2016-02-10 17:14   ` LMH
2016-02-10 17:24     ` Yaakov Selkowitz
2016-02-11 18:09       ` cyg Simple
2016-02-12 19:20         ` Warren Young [this message]
2016-02-12 21:58           ` Erik Soderquist
2016-02-12 22:42             ` Warren Young
2016-02-13  0:37               ` Erik Soderquist
2016-02-13 17:41                 ` Tony Kelman
2016-02-14  0:41                   ` Erik Soderquist
2016-02-15 14:53                     ` Eric Blake
2016-02-13 17:20             ` Corinna Vinschen
2016-02-10  2:20 ` Andrey Repin

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=4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com \
    --to=wyml@etr-usa.com \
    --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).