Mail Archives: cygwin/1998/05/09/04:11:36
I haven't checked myself if it currently does this for cdk.exe, but you
can make InstallShield print a list of what it's done. I really don't
see any problem with using it personally. I don't see a problem with
running winzip on a tar.gz file, either.
Either way works fine, but since everyone knows how to run cdk.exe and
not everyone knows winzip will handle .tar.gz files or everyone may not
even have winzip I see no reason not to use InstallShield. Plus with
InstallShield you can add registry stuff if necessary. I think
applications should be smart enough to do this on their own at runtime
if neccessary, though. That way you can dump it on a client workstation
and it works with no installation hassles.
Anyway, I can't think of a single convincing argument not to use
InstallShield if it's done right.
Jason
> -----Original Message-----
> From: Michael Lemke, Sternwarte Bamberg, Phone: +49-951-9522216
> [SMTP:ai26 AT sternwarte DOT uni-erlangen DOT de]
> Sent: Thursday, May 07, 1998 3:53 AM
> To: EPA AT datcon DOT co DOT uk
> Cc: gnu-win32%cygnus DOT com AT bamp01 DOT sternwarte DOT uni-erlangen DOT de;
> ai26 AT sternwarte DOT uni-erlangen DOT de
> Subject: RE: To use or _NOT_ to use InstallShield?
>
> In a message of Wed, 6 May 1998 09:42:09 +0100
> Received on Thu, 07 May 1998 02:20:38 MET-1MET DST
>
> Edward Avis <EPA AT datcon DOT co DOT uk> wrote
> to: 'gnu-win32 AT cygnus DOT com' <gnu-win32 AT cygnus DOT com>
>
> >It's true that to make good use of Cygwin32 you need to know
> something
> >about filesystem structure etc. However, I don't see how using
> >InstallShield is a problem in itself. If you can do something for
> the
> >user, instead of having to provide instructions and let them do it
> >themselves, then why not take the easy route?
>
> Well, I don't know what InstallShield does, seriously. But I do know
> what tar,zip etc do and how to reverse it. I hate things done behind
> my back. All these .exe files you don't know what's inside.
> Terrible.
>
>
> >
> >The installation, with the cygnus.bat placed in the start menu, lets
> the
> >user test that everything is working in the "default" configuration
> before
> >they go off and start changing things.
>
> Fine. But why not do this with a .bat file I can inspect before
> running
> it? Then I know what I am doing.
>
> >
> >As a final point, I am sure that this list would be clogged with many
> more
> >"how to install this?" questions if Cygnus went back to the old .tgz
> file
> >or whatever.
> >
>
> Maybe.
>
> So my vote is to do away with InstallShield.
>
> Michael
>
>
> --
> Michael Lemke
> Sternwarte Bamberg, University of Erlangen-Nürnberg, Germany
> (lemke AT sternwarte DOT uni-erlangen DOT de or michael AT astro DOT as DOT utexas DOT edu)
> -
> For help on using this list (especially unsubscribing), send a message
> to
> "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -