Re: [ROOT] ROOT NT installation

From: Valeri Fine (Faine) (fine@bnl.gov)
Date: Sat Jan 20 2001 - 16:57:01 MET


Hello, Dave

> I think my message must have been a bit unclear.
>
> >   I am sure I already own what Ms supplies with DevStudio,
> >   Very this gives me the  strong reason to write what I wrote
> >   above.
> >
> >   From what you said one may conclude you yourself never try what
> >   is included with MS Developer Studioto to create ROOT distribution.
>
> Indeed, I never claimed to have tried to create a Root distribution.
> Naturally I would not distribute someone else's software product as my own!

   ROOT team asked a help to CREATE the proper distribution,

> I was only saying that I thought some version of InstallShield comes with
> Visual Studio.  It may be my memory is faulty, and it was a previous version
> of VStudio(97) and not 6.0.

  No it is not your memory fault. DevStudio does include SOME version
  of InstallShield. That you never tried so you can not forget how it was performing

 That is a kind of DEMO version. It is not good to create the proper ROOT
 distribution.

> >  I did not get "what you do think". Do ROOT distribution lacks of
> >  options  to "deinstall ROOT" ? What is better from your experience
> >  "MS Installer" or "Install Shield".
>
> MS Installer is more integrated with Windows, and it is easier to create a
> basic installation package which modifies the Registry and gives options for
> custom installation of the full package.

MS installer is indeed integrated into the LAST versions of Windows OS's
It doesn't help much for Windows 95 users for example since that system has
NO registry entry to hold the evironment variables. For Window 95 one has
to edit the autoexec.bat instead.

Dave, nobody argues about Installer vs InstallShiled whatsoever.
ROOT is a free software.  One has the full access to entire ROOT source code.
One doesn't pay money to get ROOT. However one still has to pay.
It is assumed the free software users are willing to contribute just they
have a possibility and skill. The good advice are welcome as well.

> I have not provided anything except advice which was intended to be helpful
> and suggest to you that it is probably not necessary to obtain a commercial
> license for InstallShield (or any other product) in order to make an
> installation kit for Root which automatically sets path and environment
> variables.
>
> If you would like me to try to create a Root distribution (with path and
> environment set automatically), I can try to do it, although that wasn't the
> point of my message.

That was the reason of the original message from the ROOT team.

You said you had learned "Installer". That's good, please share your skill with
the rest ROOT community in the form of the proper "procedure" to create the good
ROOT distribution kit good for all Microsoft operating systems. It is very the way other
ROOT users provide the distribution for UNIX (for example people do contribute ROOT
RPMs)

At present I am a regular ROOT user trying to contribute ROOT in my spare time rather a developer . Alas I have no time NOW to
learn "Installer". That's why I prefer the "Professional version of
InstallShield". With that one can create quickly the good distribution for all known (including future) combinations of MS OS's.
There is no doubt the InstallShiled "knows" about MS Installer feature of the modern MS OS's. (see:
http://www.installshield.com/iswi/ )

So *myself* have time to create the distribution with that commercial tool. I am speaking
about myself ONLY. Somebody has another skill and experience and time and by this reason
may feel himself/herself comfortable with another tool.

I would like to call your (and ROOT team) attention Install Shield "allows you to create a single
install for Solaris, Linux, AIX, OS/400, OS/2, and Windows platforms all at once."

However the key problem is still there. It is the UNIX nature of the ROOT executable and ROOT distribution. It relies on the
environment variables. This is Ok for UNIX.
However the right "Windows" appication should rely on the registry entries and should avoid
using the environment variable at all. No "installation" tool can help resolving
this key point. And this is where the ROOT team needs some kind of the contribution
from the Windows part of the ROOT community.



  My best regards,
                        Valeri



This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:34 MET