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
From:	Dario Alcocer <alcocer AT helixdigital DOT com>
MIME-Version:	1.0
Message-ID:	<15199.13618.671411.755243@coyote.priv.helixdigital.com>
Date:	Wed, 25 Jul 2001 14:08:02 -0700
To:	cygwin AT cygwin DOT com
Cc:	Bernard Dautrevaux <Dautrevaux AT microprocess DOT com>
Subject:	RE: RPM installer (was Re: SETUP WIZARD FOR CYGWIN?XFREE86)
In-Reply-To:	<17B78BDF120BD411B70100500422FC6309E2FD@IIS000>
References:	<17B78BDF120BD411B70100500422FC6309E2FD AT IIS000>
X-Mailer:	VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid

>>>>> "Bernard" == Bernard Dautrevaux <Dautrevaux AT microprocess DOT com> writes:

    Bernard> Or as the installer user interface is tcl/tk-based, you
    Bernard> can look at FreeWrap
    Bernard> (http://home.nycap.rr.com/dlabelle/freewrap/freewrap.html). Its
    Bernard> neat and works quite well; moreover the tcl/tk installer
    Bernard> in this case do not NEED cygwin, so can unpack the basic
    Bernard> bootstrap environment without any problem).

Yes, I guess this would work as well.  However, the main reason I
didn't want eliminate the Cygwin DLL was that I wanted to use ash to
run the RPM package post-install/pre-uninstall scripts with it.  I
guess I could find a Win32 Bourne-compatible shell that didn't require
Cygwin to replace ash, but that would still leave me looking for
Win32-only ports of the other utilities that might be required by the
scripts (e.g. awk, sed, cut, paste etc.)

In the end, it just seemed simpler that, rather than trying to avoid
including Cygwin in the installer (and miss out on all that
functionality), I should instead find a way to use cygwin1.dll and
avoid the pitfalls instead.  I decided on a two-stage install process;
the first stage would check for a duplicate cygwin1.dll loaded in
memory (and abort with a message if one was found), and the second
stage would be the actual Tcl/Tk installer.

-- 
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
alcocer AT helixdigital DOT com -- http://www.helixdigital.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 -