X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=uwRa56nxSxXC1OhK
	qs8cdJQDm9eXQuDahIUA6uNM10Cl7vL3DaeJ9nQdjTUV6J2f/nxp8OPRBHdbsd6i
	iLXh6dz3imslxtv8GgtLJ8STkSNZLfxFnVmDH0bhdR5DApu4BUpRIfMUwUV8680/
	Ocm6xB76qVmE9Gkn9d5CY5QSsb8=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=ELtz/oEyMH9U8Ya6T2MH5u
	LzSwc=; b=rDIVRBB9O5ZQSj91jZBP6YaLizoje2OPVHlUDIsHRKVA0h60a+dEDa
	i31+SnucJp0gpiDyg/Q4zmg2FPBEYlE1hnGcIaHivXnMlL5sx4Vaa5dcawbtDONh
	P1WSlvCASk4XkEXB8+ukifRK1Ay9vMZUgS8vBSKfcbFUPInkO5r3o=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173017pub.verizon.net
Message-id:	<53E97753.1090809@cygwin.com>
Date:	Mon, 11 Aug 2014 22:09:23 -0400
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: update just ruby on offline cygwin installation
References:	<53E3E248 DOT 6070301 AT molconn DOT com> <53E3E71D DOT 8090208 AT cygwin DOT com> <53E94499 DOT 2080605 AT molconn DOT com> <44850477 DOT 20140812030058 AT yandex DOT ru> <53E959CC DOT 3010102 AT molconn DOT com>
In-reply-to:	<53E959CC.3010102@molconn.com>

Just to add a bit beyond what Andrey has already said.

On 08/11/2014 08:03 PM, LMH wrote:

<snip>

> 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 I let cygwin just do it's thing, it will break far
> more that it will fix. 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. 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.

Obsolete packages don't disappear all that often really.  Most likely any
package that is obsolete has just been marked as such and doesn't show up in
the list of packages by default.  If you want to see them, just uncheck
the "Hide obsolete packages" control under the list of packages on the
"Select Packages" page of setup*.exe.

> There are some post processing steps to what the server does that need a
> newer version of ruby. It would be nice to have to post processing done
> on the same server, but it is not essential. If I can update ruby
> without breaking everything else, than that is worth doing. It is not
> worth attempting to update everything just to add the post processing.

Certainly if you're very concerned about making untested changes to a
working server, you either want to work with a duplicated test version
as Andrey said or you want to off-load the post-processing piece to
another machine that's more up-to-date.  The third alternative I can
think of is that you could try to build a recent version of ruby on
your older installation.  If you have all the dependencies that would
be necessary for that, it could allow you to update ruby without
dragging allot of other useful binaries forward as well.  But this is
not without some amount of risk as well.  And I'm sure you understand
that all of this puts you in the realm of needing to support this
installation yourself.  I expect that's not a big deal to you since
it has been working fine for you and you've been doing this already.
So I'm stating the obvious I'm sure. :-)


<snip>


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

- Raw text -