public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen John Smoogen <smooge@gmail.com>
To: cygwin@cygwin.com
Cc: fergus@bonhard.uklinux.net
Subject: Re: New Cygwin "setup" program useless on my Win-XP box. Not very nice at all.
Date: Tue, 08 Nov 2016 14:18:00 -0000	[thread overview]
Message-ID: <CANnLRdiVmJ=oHMQwkFGQfq5s2_kHRX=fcO67k99BSwgV+gJa-w@mail.gmail.com> (raw)
In-Reply-To: <000601d239bc$dd8f0be0$98ad23a0$@bonhard.uklinux.net>

On 8 November 2016 at 07:37, Fergus <fergus@bonhard.uklinux.net> wrote:
>> WinXP is not supported. Complain as you wish, write as long a posts as you
> were, it won't change.
>> If you need old, outdated and unsupported OS, go into old, outdated and
> unsupported Cygwin Time Machine.
>
> Hang on, this is just a bit dismissive. Years ago the Cygwin nobility gave
> us all loads of warning of the demise of v.1.5 (the last installation that
> could be used on W95/98); they took fantastic trouble over supplying - and
> deploying to mirrors - the last relevant sources under release-legacy/ with
> an associated setup-legacy.ini AND an associated setup-legacy.exe to set the
> whole thing up. And, finally, seven or more years on, this version is still
> available: see, for example,
> http://ftp.uni-kl.de/pub/windows/cygwin/.
>
> No such efforts with the last available XP version. Come on, the Time
> Machine is really hard to navigate. It would have been really helpful to do
> for XP exactly what was done for 95/98: petrify the last relevant sources
> along with .ini and .exe, re-label conveniently and obviously, and upload to
> mirrors.
>

The world has changed greatly since that time. Cygwin is no longer a
product with an income stream that can cover costs of admins,
developers and legwork. It is done by volunteers at Red Hat (Corinna
and Yaakov's jobs are now primarily linux kernel development and other
work). Yes it would be great if that work had been done and if someone
wants to help and do that work, it would be really helpful.

I am saying this as someone who made such suggestions and didn't do
the work to help them. Guilty as charged. I can see what I can do over
my Winter break but it will be a month or more before it happens.

> Could this not still be done? Sure, continuing usage of XP carries its own
> risks, but that's a quite different issue.
>
> Fergus
>
>
> --
> 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
>



-- 
Stephen J Smoogen.

--
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-11-08 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 12:37 Fergus
2016-11-08 14:18 ` Stephen John Smoogen [this message]
2016-11-08 16:54 ` Ken Brown
  -- strict thread matches above, loose matches on Subject: below --
2016-11-10  7:25 Fergus
2016-11-07 18:18 Rus
2016-11-07 18:24 ` Erik Soderquist
2016-11-07 18:35 ` 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='CANnLRdiVmJ=oHMQwkFGQfq5s2_kHRX=fcO67k99BSwgV+gJa-w@mail.gmail.com' \
    --to=smooge@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=fergus@bonhard.uklinux.net \
    /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).