Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Fri, 12 Dec 2003 17:45:38 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Third-party products that include cygwin
Message-ID:	<20031212224538.GB4582@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3D848382FB72E249812901444C6BDB1D022F46DE AT exchange DOT timesys DOT com>
Mime-Version:	1.0
In-Reply-To:	<3D848382FB72E249812901444C6BDB1D022F46DE@exchange.timesys.com>
User-Agent:	Mutt/1.4.1i

On Fri, Dec 12, 2003 at 05:04:11PM -0500, Robb, Sam wrote:
>>>An alternative is a nice automated way in their installer to invoke the
>>>Cygwin installer.
>>
>>Heh...  that would IMO require setup.exe to be able to do batch runs.
>>Not possible, unless changes has been done very recently.
>
>Huh?  We've been doing things that way with our software installer for
>a good 6-9 months now, using a version of setup.exe built from a CVS
>snapshot.  If the user needs Cygwin installed prior to installing our
>sofware, we kick off setup.exe and let it do it's thing.

I think this is how the BitKeeper folks do it, too, FWIW.

cgf

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

- Raw text -