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: <3B5EEBBD.1000202@ece.gatech.edu>
Date: Wed, 25 Jul 2001 11:54:37 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Dario Alcocer <alcocer AT helixdigital DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: RPM installer (was Re: SETUP WIZARD FOR CYGWIN?XFREE86)
References: <Pine DOT GSO DOT 3 DOT 95-heb-2 DOT 07 DOT 1010724150418 DOT 6324K-100000 AT csd>	<001201c11440$f5acf5a0$806410ac AT local>	<20010724112652 DOT G9776 AT redhat DOT com>	<3B5DA52D DOT 2020304 AT ece DOT gatech DOT edu>	<13435078840 DOT 20010724210651 AT logos-m DOT ru> <15198 DOT 58300 DOT 305187 DOT 207197 AT coyote DOT priv DOT helixdigital DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Sounds cool, Dario.  How have your db and rpm ports been generated? 
Which versions are you using, db-3 and rpm-4, or db-2 and rpm-3 ?  Is db 
built as a dll, or as a static lib ?

BTW, for your purposes perhaps you could pack up your bootstrap 
environment into a self-extracting zip file ?

--Chuck

Dario Alcocer wrote:


> Egor, it's very interesting that you mention this approach to
> bootstrapping RPM.  I've in fact built an initial working version of a
> Tcl/Tk GUI installer using the *exact* approach you mention, using a
> small Cygwin bootstrap environment (rpm.exe, sh.exe, mount.exe
> cygwin1.dll, and other necessary programs.)
> 
> The installation is performed in two steps:
> 
> 1. Create the necessary directories and mounts, unpack rpm binary tar,
>    then run 'rpm --initdb'
> 
> 2. Run rpm to install RPM files.
> 
> All the install related tasks (cygwin.bat creation, installing bash
> short-cut, running mkpasswd and mkgroup, etc.) are performed by RPM
> post-install scripts.
> 
> Best part is, it actually *works*.  I've not completed all the work on
> it (I've been too busy with several consulting gigs to spend more than
> 3-5 hours per week on it.)  However, I now have a staff member that's
> tying up the loose ends and getting it ready for actual use (I plan on
> using the Tcl/Tk installer in my consulting work.)  The main
> limitation now is that there isn't a self-extracting mechanism worked
> out yet that would create the bootstrap environment before launching
> the Tcl/Tk GUI installer.  For my purposes, I was planning on creating
> CDs with the necessary bootstrap environment pre-unpacked, so this
> would only be an issue for trying to support a self-contained
> network-based installer like the current setup.exe.  This is not an
> insurmountable problem, so I expect to have something implemented for
> this feature eventually.
> 
> Anyway, at some point I'd like to be able to offer it to the Cygwin
> project.  Unfortunately, it's still very immature to be widely
> released, which is why I had not suggested or mentioned it before.
> Nevertheless, if any of you are interested in playing around with the
> installer, I could put a CD-ROM .iso image (~13MB) up on my web site
> eventually when the work is done (I hope to have a very rough first
> release by the middle of August.)




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