public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: Dario Alcocer <alcocer@helixdigital.com>
Cc: cygwin@cygwin.com
Subject: Re: RPM installer (was Re: SETUP WIZARD FOR CYGWIN?XFREE86)
Date: Wed, 25 Jul 2001 08:54:00 -0000	[thread overview]
Message-ID: <3B5EEBBD.1000202@ece.gatech.edu> (raw)
In-Reply-To: <15198.58300.305187.207197@coyote.priv.helixdigital.com>

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/

  reply	other threads:[~2001-07-25  8:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.3.95-heb-2.07.1010724150418.6324K-100000@csd>
     [not found] ` <001201c11440$f5acf5a0$806410ac@local>
     [not found]   ` <20010724112652.G9776@redhat.com>
     [not found]     ` <3B5DA52D.2020304@ece.gatech.edu>
2001-07-24 10:10       ` SETUP WIZARD FOR CYGWIN?XFREE86 egor duda
2001-07-24 10:38         ` Bobby McNulty
2001-07-24 11:32           ` Mailing list etiquette [Was: Re: SETUP WIZARD FOR CYGWIN?XFREE86] Charles Wilson
2001-07-24 12:17             ` Christopher Faylor
2001-07-24 11:34           ` SETUP WIZARD FOR CYGWIN?XFREE86 Charles Wilson
2001-07-24 12:05             ` Charles Wilson
2001-07-24 12:19               ` Sorry (Was Re: SETUP WIZARD FOR CYGWIN?XFREE86) Bobby McNulty
2001-07-25  8:20         ` RPM installer (was " Dario Alcocer
2001-07-25  8:54           ` Charles Wilson [this message]
2001-07-25 13:59             ` Dario Alcocer
2001-07-25 19:25               ` Rue. SATOH
2001-07-26  8:43                 ` Dario Alcocer
2001-07-26 17:53                   ` Rue. SATOH
2001-07-25 11:20 Bernard Dautrevaux
2001-07-25 14:08 ` Dario Alcocer
2001-07-25 16:23   ` Robert Collins
2001-07-25 16:33     ` Charles Wilson
2001-07-26  8:36       ` Dario Alcocer
2001-07-26 16:49         ` Robert Collins
2001-07-26 18:45         ` Charles Wilson
2001-07-26  8:30     ` Dario Alcocer
2001-07-26 16:44       ` Robert Collins
2001-07-26 17:49         ` Dario Alcocer
2001-07-27  4:57           ` Robert Collins
2001-07-27  5:59             ` egor duda
2001-07-27  7:33               ` Robert Collins
2001-07-27  7:48                 ` Borsenkow Andrej
2001-07-27 15:04                   ` Robert Collins
2001-07-28  0:12                     ` Borsenkow Andrej
2001-07-27  8:19                 ` egor duda
2001-07-27 18:32                   ` Robert Collins
2001-07-27  8:50                 ` Dario Alcocer
2001-07-27 21:12                 ` Jonadab the Unsightly One
2001-07-26 18:34         ` Charles Wilson
     [not found] <EC421C2230BBD211A11400805FA7784D25DDED@express8.res.utc.com>
2001-07-26  8:46 ` Dario Alcocer
2001-07-27  3:06 Bernard Dautrevaux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B5EEBBD.1000202@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=alcocer@helixdigital.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).