From: Andrey Repin <anrdaemon@yandex.ru>
To: LMH <lmh_users-groups@molconn.com>, cygwin@cygwin.com
Subject: Re: update just ruby on offline cygwin installation
Date: Tue, 12 Aug 2014 00:50:00 -0000 [thread overview]
Message-ID: <669445082.20140812044151@yandex.ru> (raw)
In-Reply-To: <53E959CC.3010102@molconn.com>
Greetings, LMH!
> The problem I have is that cygwin has a tendency to remove depreciated
> packages when updating. This is an older setup and there are critical
> components in the build that are no longer available in more recent
> cygwin packages.
If this is a "critical setup", then you should have a test environment
replicating your setup, to do any experimentation before deploying changes on
live system.
That's the basics of "critical environment" handling.
> If I let cygwin just do it's thing, it will break far more that it will fix.
Following your logic, we should never upgrade, and use DOS 1.0 on our
machines.
> Updating the entire cygwin install would mean moving to more recent versions
> of multiple packages and who knows how much time, effort, and resources
> would be involved in fixing all of that.
Nobody know, unless someone try it.
This list only providing support for current packages.
We'll do our best to help you resolve any issues that might arise from
upgrade, but it's unlikely anyone would see into any issues coming from
obsolete installs.
Sorry.
> At the moment, the server does exactly what it needs to in its
> current configuration, so there is little sense in wading into the
> quagmire of updates when there is little or noting to be gained.
Fail logic. Worse, it's presumptuous. The gain is rather obvious: better
interprocess- and system compatibility.
I.e., for Cygwin itself - lots of fork-related fixes for the past year.
There's also many other packages, which have been fixed/upgraded for similar
reasons.
To the more technical of your questions: yes, largely.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 12.08.2014, <04:30>
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2014-08-12 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 20:32 LMH
2014-08-07 20:53 ` Larry Hall (Cygwin)
2014-08-11 22:33 ` LMH
2014-08-11 23:05 ` Andrey Repin
2014-08-12 0:03 ` LMH
2014-08-12 0:50 ` Andrey Repin [this message]
2014-08-12 2:10 ` Larry Hall (Cygwin)
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=669445082.20140812044151@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=lmh_users-groups@molconn.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).