From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129748 invoked by alias); 4 Mar 2019 12:06:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 129740 invoked by uid 89); 4 Mar 2019 12:06:01 -0000 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 Received: from co03.mbox.net (HELO co03.mbox.net) (165.212.64.33) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 04 Mar 2019 12:05:59 +0000 Received: from co03.mbox.net (localhost [127.0.0.1]) by co03.mbox.net (Postfix) with ESMTP id 44Cdyr52Hjzq2J8 for ; Mon, 4 Mar 2019 12:05:56 +0000 (UTC) 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 Received: from ca31.cms.usa.net [165.212.11.131] by co03.mbox.net via smtad (C8.MAIN.4.17D) with ESMTP id XID013XcDmF14434X03; Mon, 04 Mar 2019 12:05:52 -0000 X-USANET-Source: 165.212.11.131 OUT kdbotts@usa.net ca31.cms.usa.net CLR X-USANET-MsgId: XID013XcDmF14434X03 Received: from web13.cms.usa.net [165.212.8.213] by ca31.cms.usa.net (ESMTP/kdbotts@usa.net) via mtad (C8.MAIN.4.10M) with ESMTP id 508XcDmF10336M31; Mon, 04 Mar 2019 12:05:52 -0000 X-USANET-Auth: 165.212.8.213 AUTO kdbotts@usa.net web13.cms.usa.net CLR Received: from 73.247.78.3 [73.247.78.3] by web13.cms.usa.net (USANET web-mailer C8.MAIN.4.16Q); Mon, 04 Mar 2019 12:05:52 -0000 Date: Mon, 04 Mar 2019 12:06:00 -0000 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 Content-Transfer-Encoding: quoted-printable Z-USANET-MsgId: XID508XcDmF10336X31 X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00027.txt.bz2 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 subse= t: no X, no apache, no big database servers, etc: just basic command line tool= s.) 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 o= ne 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 mirro= rs, has been built against cygwin-3 base. Am I reasonably safe to assume it wi= ll still work with cygwin-2.11.2? Does this generalize to all, or at least mo= st, other packages? Thank you all for your advice. --- Karl Botts, kdbotts@usa.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