From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116709 invoked by alias); 5 Mar 2019 19:09:39 -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 116672 invoked by uid 89); 5 Mar 2019 19:09:36 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=rolling, Hx-spam-relays-external:ESMTPA X-HELO: vsmx009.vodafonemail.xion.oxcs.net Received: from vsmx009.vodafonemail.xion.oxcs.net (HELO vsmx009.vodafonemail.xion.oxcs.net) (153.92.174.87) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Mar 2019 19:09:34 +0000 Received: from vsmx001.vodafonemail.xion.oxcs.net (unknown [192.168.75.191]) by mta-5-out.mta.xion.oxcs.net (Postfix) with ESMTP id 128CFC0499 for ; Tue, 5 Mar 2019 19:09:30 +0000 (UTC) Received: from Gertrud (unknown [87.185.218.207]) by mta-5-out.mta.xion.oxcs.net (Postfix) with ESMTPA id D57FA30026C for ; Tue, 5 Mar 2019 19:09:27 +0000 (UTC) From: Achim Gratz To: cygwin@cygwin.com Subject: Re: Cygwin-3 and the Bleeding Edge References: <152XcDme12976Set.1551701152@web13.cms.usa.net> Date: Tue, 05 Mar 2019 19:09:00 -0000 In-Reply-To: <152XcDme12976Set.1551701152@web13.cms.usa.net> (KARL BOTTS's message of "Mon, 04 Mar 2019 06:05:52 -0600") Message-ID: <87pnr587fg.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2019-03/txt/msg00071.txt.bz2 KARL BOTTS writes: > Are cygwin packages being pushed to mirrors still compatible with > cygwin-2.11.2, now that cygwin-3 has entered the release pipeline? Cygwin, for better or worse, is a rolling distribution. If that doesn't suit your needs, you'll have to come up with your own mechanism to lock things the way you want it to. In this particular case, Cygwin 3.0 does add new API and if any new package uses it, then it will become incompatible with the older Cygwin. While I can't speak for other package maintainers, I usually fully update Cygwin before building new packages. > 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. =E2=80=A6which was built long before the API change in question. > So: Assume for the moment that the latest git package release on the mir= rors, > 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? No. You need to keep the dependency chain ordered so that all dependencies of the package to be installed are older than the package itself. While setup now supports versioned dependencies in principle, this is not currently used, so you'll have to do this via other means. Regards, Achim. --=20 +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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