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: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= 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:date:from:to:subject:mime-version:message-id :content-type:content-transfer-encoding; s=default; bh=Bx2CQtQiv TvkTvkJ6Jjp4DKerFg=; b=uVrBjCdQqmluo94rqemaSiPeVT1HMIphgm9DBICLu S16Mf3Sy17RDfKKTaBP0WWudwdDCxEa8o1EZdMYvnWZ12rZaF0mLdyG1LLFQDy59 GTQpIpvf2Eibu8tuUNPhrlk0/VwvlwqgjMLRGDR1D7RvurN8yejNWuJCsWb6HCnh wA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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-Spam-SWARE-Status: No, score=-7.6 required=5.0 tests=BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=burn, bleeding, traffic, awhile X-HELO: co03.mbox.net X-USANET-Received: from co03.mbox.net [127.0.0.1] by co03.mbox.net via mtad (C8.MAIN.4.17E) with ESMTP id 772XcDmF17584M03; Mon, 04 Mar 2019 12:05:52 -0000 X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-Routed: 3 gwsout-vs Q:bmvirus X-USANET-GWS2-Tenant: usa.net X-USANET-GWS2-Tagid: UNKN X-USANET-Source: 165.212.11.131 OUT kdbotts AT usa DOT net ca31.cms.usa.net CLR X-USANET-MsgId: XID013XcDmF14434X03 X-USANET-Auth: 165.212.8.213 AUTO kdbotts AT usa DOT net web13.cms.usa.net CLR Date: Mon, 04 Mar 2019 06:05:52 -0600 From: "KARL BOTTS" To: 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 X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x24C6AHB021856 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