Darryl Okahata <darrylo(a)sr.hp.com> writes:
> [ Olivier, please point out to RMS that Cygnus is using InstallShield to
> distribute the gnu-win32 binaries (which include many/most GNU
> programs). ]
>
> Samuel Mikes <smikes(a)alumni.hmc.edu> wrote:
>
> > It should be possible to define the setup so that it looks
> > something like this, when burned on CD-ROM:
> >
> > /SETUP32.EXE
> > /(installshield data files)
> > /(.CAB files)
> > /XEmacs/
> > /XEmacs/src/
> > /XEmacs/lisp/
> > ... other XEmacs sources
> > /InstallShield/(script and data files)
>
> I'd like to emphasize that the XEmacs binaries/sources that will be
> installed are stored in the .CAB files. The XEmacs/src, etc. trees are
> there only for convenience (so that people could easily pick out a file
> or two without having to re-run the setup program, etc.).
>
> Also, the other versions of InstallShield allow you to package up all of
> the InstallShield and XEmacs files into a single monolithic executable,
> for easy distribution (users only have to download one, possibly large,
> file). This is the most useful form. Basically, to install the
> software, the user simply runs the monolithic executable. All of the
> files are automatically extracted from the monolithic executable, and the
> real setup program is then automatically executed.
This is really no different than publishing a XEmacs RPM for linux, .deb
for debian linux, solaris installable package, or a SMIT installable
package for AIX.
Just do it. :) I haven't done any installshield programming in 3 years,
but if anybody needs gruntwork, lemme know, I might be able to remember.
-Bill P.