Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 13 Mar 2003 13:29:38 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.3.21-1 Message-ID: <20030313182938.GA1808@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030313071238 DOT A65230 AT reliant DOT immure DOT com> <20030313165328 DOT GB32644 AT redhat DOT com> <20030313112334 DOT A66871 AT reliant DOT immure DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030313112334.A66871@reliant.immure.com> User-Agent: Mutt/1.5.1i On Thu, Mar 13, 2003 at 11:23:34AM -0600, wayne wrote: >On Thu, Mar 13, 2003 at 11:53:28AM -0500, Christopher Faylor wrote: >> On Thu, Mar 13, 2003 at 09:48:33AM -0500, Igor Pechtchanski wrote: >> > ;-) >> > Igor >> >> Agh, no. This isn't a PTC situation. >> >> Requiring specific cygwin releases is not a path we want to go down. >> How many times does it have to be said? The cygwin1.dll name doesn't >> change because it is supposed to always *work*. If you require a >> specific release you're making a mistake. >I already have a issue with the latest release that is why I mentioned >it. Sure. Ok. So you stabilize on a version of cygwin for your company. That's fine. I don't see that as a justification for allowing all previous versions of cygwin to be installed. If there was a different release model where we could be insured of having all packages working together that would be different. That's not the we we're doing things in cygwin, though. You can argue that we're doing things wrong but it would certainly be confusing to allow the installation of cygwin 1.3.1 along with the latest version of ssh which doesn't work with 1.3.1. We already have that problem with the 'prev' version of cygwin but at least that's fairly manageable. Allowing 27 different varieties of the DLL just doesn't seem like it would be a win. I can easily envision the "why doesn't ssh work with 1.3.1?" messages here. I'm sure that what you're doing is essentially doing a standard "release" for your own internal release. You've come up with a set of packages and a cygwin DLL which works nicely together. That's fine. I just don't think that this is something we want to support in setup, in general. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/