This is the mail archive of the
mailing list for the Cygwin project.
Re: CD-based distribution (was Another website....)
- To: Geoffrey Noer <noer at cygnus dot com>
- Subject: Re: CD-based distribution (was Another website....)
- From: Jeff Sturm <jsturm at sigma6 dot com>
- Date: Fri, 14 Aug 1998 09:46:57 -0400
- CC: Marcus Brown <Brown at sw dot mke dot etn dot com>, Robert Read <rread at datarithm dot com>, Robert dot Cross at scottish-newcastle dot co dot uk, gnu-win32 at cygnus dot com
- References: <C0B7E1B3BE9CD111B6F000A0246DBB9B16EF@softech.mke.etn.com> <19980813075556.C12323@cygnus.com>
Geoffrey Noer wrote:
> On Wed, Aug 12, 1998 at 01:49:44PM -0500, Marcus Brown wrote:
> > Well, I couldn't really say anything about the Debian tools since I've
> > never used the Debian distribution, only RedHat and Slackware. The rpm
> > port to cygwin32 that I have seen is solid, and works fine with source
> > rpms (haven't tried binary so don't quote me on this :). If there is a
> > better or more convenient way to package distributions I'd be glad to
> > take a look at it, rpm is the first thing that came to mind. A more
> > pressing issue would seem to be what would actually be included in this
> > distribution...
> In principle, I would prefer InstallShield-based distributions but
> obviously that causes a lot of problems -- it's proprietary and isn't
> very scalable to 100s of packages. So maybe rpm is the way to go...
> Overall, I think it is best if the system promotes compatibility with
> Windows. (We'd all be much better off running Linux if all we wanted
> was a UNIX box). If there is a good way to package things that is
> more in keeping with normal Windows ways of existance other than
> Installshield that might be a better choice. Dunno.
Packaging each and every component with InstallShield would be a
mistake. I would prefer to use rpm, since it is flexible and
well-supported, but still use InstallShield (or a similar utility) to
build a graphical front-end. A SETUP.EXE program can automatically
invoke rpm for the core components, and a custom install may prompt the
user with a list of optional components, similar to the glint tool with
I hope to get some time in the following weeks to try this out. If
anyone knows good alternatives to InstallShield (preferably free) I'd
like to hear them. We own and use InstallShield here but I'm not too
sure about the legal implications of using a proprietary installer with
a GPL distribution...
For help on using this list (especially unsubscribing), send a message to
"email@example.com" with one line of text: "help".