From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85277 invoked by alias); 12 Feb 2016 19:20:26 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 85265 invoked by uid 89); 12 Feb 2016 19:20:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=anticipation, H*MI:sk:0JN2rG-, H*MI:sk:tyUdg@m, H*MI:sk:56BB6FD X-HELO: etr-usa.com Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 12 Feb 2016 19:20:24 +0000 Received: (qmail 98892 invoked by uid 13447); 12 Feb 2016 19:20:23 -0000 Received: from unknown (HELO polypore.west.etr-usa.com) ([73.26.17.49]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 12 Feb 2016 19:20:23 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Last Version of Cygwin for XP From: Warren Young In-Reply-To: <56BCCE7D.6040605@gmail.com> Date: Fri, 12 Feb 2016 19:20:00 -0000 Content-Transfer-Encoding: quoted-printable Message-Id: <4D4ECA09-53B3-4A16-89BC-E9C7054A22C7@etr-usa.com> References: <56BA9DB2.3080106@cygwin.com> <56BB6FD1.6000208@molconn.com> <56BB7220.5010101@cygwin.com> <56BCCE7D.6040605@gmail.com> To: The Cygwin Mailing List X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00174.txt.bz2 On Feb 11, 2016, at 11:10 AM, cyg Simple wrote: >=20 > 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=E2=80= =99s a lot of overlap between the group of people unwilling to upgrade thei= r XP boxes and the group willing to install development tools, clone git re= pos, backport patches from trunk, and build local DLLs. If there were a large overlap, Red Hat wouldn=E2=80=99t be raking in billio= ns supporting 10-year-old Linux boxes. That begs a question: Is there a market for a =E2=80=9CCygwin LTS=E2=80=9D = service, where someone does all that backporting for a tiny recalcitrant mi= nority of Windows XP + Cygwin users? Who knows, maybe there=E2=80=99s a ne= w 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=E2=80=99s 2= 2 months of unfixed security problems, bugs, and regressions with respect t= o 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=E2=80=99t jettisoned XP support yet is that it=E2= =80=99s more work than ignoring that old code. Eventually, Cygwin=E2=80=99s gonna have to scrape that barnacle off the hul= l. You should already have your Cygwin XP install trees packed up in antic= ipation of that day. > The problem will be the other packages that stop support of older > Cygwin versions. That=E2=80=99s why you archive your installation tree. And for those without that foresight and preparedness, there=E2=80=99s 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