delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/11/19/15:03:17

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <20011119200231.6142.qmail@web20008.mail.yahoo.com>
Date: Mon, 19 Nov 2001 12:02:31 -0800 (PST)
From: Joshua Franklin <joshuadfranklin AT yahoo DOT com>
Subject: Re: installshield replacement
To: cygwin AT cygwin DOT com
In-Reply-To: <3BF96295.7D042225@ece.gatech.edu>
MIME-Version: 1.0

> No, setup is not based on cygwin1.dll.  It is a pure
> windows app -- and
> can be used (with appropriate modifications, of
> course) to install
> non-cygwin software.  E.g. the XEmacs project is
> using a fork of our
> setup to install its software and packages.
I didn't mean to suggest that setup.exe depends on
cygwin1.dll, just that it was designed to install
things that do. And, there are already projects that
are designed to install anything without modification
(just a script), so you don't have to make source
changes. The exception is the UNIXy tool, like XEmacs,
for which setup.exe's peculiarities might be handy.


__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019