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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	q=dns; s=default; b=heLTX9zWPfCQnxAg9/oPikF2o8PJcC0++6nN56Kt8KW
	p0Kym5XW83572xqGH/COyCbiL4WARR7looW1n6yjY0lt/YXlOq94bCQVaVl1uiaw
	A6Kwyo+W3I5+xCTgGhnyhhiD4QYBtrkYDxX3MnMBcjq8TXnS60ir4fSb++hu3Uqw
	=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	s=default; bh=yfoMbeuYy9/binJkGuM7v/UkDY8=; b=YAztdkNI5eXkc7xIH
	Bue1heVq4hKjGi2Ls4BbLSZiIcKOnGuMJsAYFd5YzKyDTgyA4Mi1mZt92OBK2OGc
	MFVO2n0HsKGvO0tv7dVyXsWvMUY+fgGrHIwbPt8IedGjWIyaU7G5riY2zYKOhBaz
	r4tfr8jGtRRAo8VKYfYVAv94Lc=
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-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
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin-3 and the Bleeding Edge
References:	<152XcDme12976Set DOT 1551701152 AT web13 DOT cms DOT usa DOT net>
Date:	Tue, 05 Mar 2019 20:09:23 +0100
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id x25J9mFv025878

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.

…which was built long before the API change in question.

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

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.
-- 
+<[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

- Raw text -