X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Wed, 19 Mar 2008 00:06:47 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: FAQ suggestion
Message-ID: <20080319040647.GE22446@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <a71bd89a0803181415w18070c8u59c3091defcb1a5b@mail.gmail.com> <20080318232317.GA22446@ednor.casa.cgf.cx> <dd3cefac0803181733v2cc1f3d1le14bac203b77d09e@mail.gmail.com> <47E088E3.2080504@cygwin.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47E088E3.2080504@cygwin.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Tue, Mar 18, 2008 at 11:30:43PM -0400, Larry Hall (Cygwin) wrote:
> Adam Thompson wrote:
>> On 18/03/2008, Christopher Faylor wrote:
>>>  So, we DON'T WANT people doing this.  What we actually want a 3PP to do
>>>  is check if there is a version of cygwin installed and use the installed
>>>  version if it is a newer or conditionally upgrade if it is not.
>>>
>> The problem with this is that it requires the immediate and total
>> cooperation of all 3PPs.
>> Sure - Acme Software might change their application to check for a
>> pre-existing instance of Cygwin, and let's say it finds one being used
>> for KillerApp 1.5.  All well and good.
>> The next time the user re-installs or updates Killer App 1.5, if it
>> doesn't do the check, it breaks Acme's software.
>> Unfortunately, KillerApp Co take the view of "well, our software still
>> works, it must be a problem with Acme".
>> A package designed to do these checks would certainly be a good idea,
>> but it isn't going to happen (be adopted) overnight, and in the
>> meantime, the option of having an isolated cygwin environment is very
>> alluring.  So tempting in fact, that I've been considering recompiling
>> with a view to stopping 3rd party apps breaking the sshd which is on
>> our base Win2K3 build.
>
> I feel like I'm caught in a temporal causality loop...

.egnarts fo tros leef I  .etunim a tiaW  !oot em ,yeH

fgc

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

