DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:mime-version:message-id
	:content-type:content-transfer-encoding; q=dns; s=default; b=Dyr
	jwEhmco8ulZkHS9lEP/hZGacSBTjLCC0G0mQYTPBaiF/J5KcTyJlmbgdJVSiwRWq
	81YMe+Bh6aqhcLrLu5cVH5mSWotbC248jmINYrPbKInEm8ak7ag1RaO6p+BvNxyC
	riofg0rN85eY7FI7GmnCjgzkoondKBFWE/HKO2B4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 04 Mar 2019 06:05:52 -0600
From: "KARL BOTTS" <kdbotts AT usa DOT net>
To: <cygwin AT cygwin DOT com>
Subject: Cygwin-3 and the Bleeding Edge
Mime-Version: 1.0
Message-ID: <152XcDme12976Set.1551701152@web13.cms.usa.net>
Content-Type: text/plain; charset=ISO-8859-1
Z-USANET-MsgId: XID508XcDmF10336X31
Content-Transfer-Encoding: 8bit


Are cygwin packages being pushed to mirrors still compatible with
cygwin-2.11.2, now that cygwin-3 has entered the release pipeline?

I have several machines set up with cygwin.   (It is a pretty minimal subset:
no X, no apache, no big database servers, etc: just basic command line tools.)
 I try to keep the machines exactly in sync.  I generally update cygwin once
or twice a year, and sync all the machines to the same version of cygwin at
about the same time.  I have been doing this for many years, and have a
procedure that works well for me.  (Roughly, I use cygwin-setup to update one
machine, test and burn it in for a few days, and then clone it to the other
machines by other means.)

I try to avoid the "bleeding edge".  I follow the cygwin mailing list, and try
_not_ to take a new major version of base cygwin until it settles down, in
terms of mailing list traffic.  Right now, it feels to me like I should wait
awhile before moving to cygwin-3.

But now and then I need to upgrade a specific package outside of my full
cygwin update cycle.  E.g., right now I would like to upgrade just git.

So:  Assume for the moment that the latest git package release on the mirrors,
has been built against cygwin-3 base.  Am I reasonably safe to assume it will
still work with cygwin-2.11.2?  Does this generalize to all, or at least most,
other packages?

Thank you all for your advice.


---
Karl Botts, kdbotts AT usa DOT net


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