Hello Nick,
Can you elaborate which troubles you found
with InstallShields and why do you think it is not safe?
It does change the autoexec.bat file to make the life of the average
users simpler and it does preserver the copy of the original
autoexec.bat file to allow the advanced user adjusting things.
If fact one adopt another approach, namely make the life of the advanced
user simpler and complicate the simple user life. I mean the
installation may not touch autoexec and ask the user to it him/herself.
I can not say whether this is better. However I think my approach gives
some favor for the average users.
In any case I would like to mention the "procedure" in question is
software program. This implies it may have been delivered with some bug
to be fixed.
The installation the code of the installation procedure from
http://root.bnl.gov is kept in CVS repository.
(see: http://root.bnl.gov/QtRoot/QtRoot.html#source )
As usually any feedback positive / negative / constructive (especially
one from Nick :-) is welcome !!!
My best regards, Valeri
> -----Original Message-----
> From: Nick van Eijndhoven [mailto:Nick@phys.uu.nl]
> Sent: Wednesday, November 13, 2002 6:07 AM
> To: Rene Brun
> Cc: GENTIT Francois-Xavier DAPNIA; 'Faine, Valeri';
> 'roottalk@pcroot.cern.ch'
> Subject: Re: [ROOT] Do not install ROOT in "Program Files"
>
> Hi Rene,
> I fully agree with dropping the install shield release.
> The "good old tar file" releases are very reliable, easy
> to install and much safer than the install shield procedure.
>
> Cheers,
> Nick.
>
> --
> Dr. Nick van Eijndhoven mailto:nick@phys.uu.nl
http://www.phys.uu.nl/~nick
>
------------------------------------------------------------------------
--
> Org.: Utrecht University, Faculty of Physics and Astronomy
> Address: Princetonplein 5, NL-3584 CC Utrecht, The Netherlands
> Phone: +31-30-2532331(direct) +31-30-2531492(secr.) Fax:
+31-30-2518689
> CERN: +41-22-7679751(direct) +41-22-7675857(secr.) Fax:
+41-22-7679480
> Offices: Buys Ballot laboratory Room 710 (Utrecht) B23 1-020 (CERN)
>
------------------------------------------------------------------------
--
>
>
> Rene Brun wrote:
> >
> > Hi Francois-Xavier,
> >
> > Since this discussion is hard to follow for the majority of ROOT
users,
> > I propose the following solution:
> > The problems reported are exclusively with the InstallShield
> distribution.
> > I propose to not build this mode of distribution for Windows anymore
> > and to provide only the "good old tar file".
> > Based on the ftp distribution statistics, I see that we had
> > 7155 distributions of the "good old tar file"
> > 1423 distributions of the InstallShield file.
> >
> > At each Root release, I spend more time building the 3 Windows files
> > than the 25 Unix tar files. Suppressing the InstallShield file will
save
> > me some time and also time to Windows users.
> >
> > Unless I get many complaints, I will drop the InstallShield file
> > in the coming releases.
> >
> > Rene Brun
> >
> > On Wed, 13 Nov 2002, GENTIT Francois-Xavier DAPNIA wrote:
> >
> > > Hello Valeri,
> > > I would hesitate between 2 solutions:
> > > (1) - your solution 3.
> > > (2) - a 4th possibility, which simply consists in doing nothing
and
> > > advise users not to put ROOT in a directory with a blank in the
name.
> > > You should take the decision with René and the ROOT staff. In
case
> your
> > > solution 3 is adopted, please modify the makefile which is
provided
> with
> > > ROOT in root/test.
> > >
> > > François-Xavier Gentit
> > > DAPNIA/SPP CEA Saclay
> > > http://gentit.home.cern.ch/gentit/
> > >
> > >
> > >
> > > -----Message d'origine-----
> > > De : Faine, Valeri [mailto:fine@bnl.gov]
> > > Envoyé : mardi 12 novembre 2002 17:14
> > > À : GENTIT Francois-Xavier DAPNIA
> > > Cc : roottalk@pcroot.cern.ch
> > > Objet : RE: [ROOT] Do not install ROOT in "Program Files"
> > >
> > >
> > > Hello François,
> > >
> > > Thank you very much for you example. That has allowed me to
understand
> > > the user's need better.
> > >
> > > The bottom line:
> > > ----------------
> > > If the file name contains any special symbol or blank it must have
> been
> > > advised to quote this file name. This approach should work for
either
> > > platform, since the modern UNIX systems do allow the blanks and
the
> > > special symbols for the file names also.
> > >
> > > Anyway . . .
> > >
> > > There are three different solutions here:
> > >
> > > 1. I can add for both kind of platforms namely Win9<x> and NT<x>
> > > one extra env. variable. Let's call it ROOTPATH, that is to
contain
> the
> > > "short" version of ROOTSYS with no blank.
> > > (Try the command prompt command "dir /X c:\ " to reveal the short
> names)
> > > This variable had been done with Win9x installation (try
> > > http://root.bnl.gov) and can be done for NT<x> as well.
> > > (Cons: one can change the NTFS setting to prevent it to generate
the
> > > short names)
> > >
> > > For example:
> > > > dir /X c:\
> > > . . .
> > > 11/07/2002 10:21a <DIR> PROGRA~1 Program
Files
> > > . . .
> > >
> > > 2. As p.1 above but ROOTSYS itself is to be assigned in short form
> right
> > > away, no extra ROOTPATH is needed.
> > >
> > > 3. Adjust your makefile (see attachment)
> > >
> > > Can you try to change your makefile.
> > > I propose to add one extra variable
> > > Let's say:
> > >
> > > ROOTPATH = "$(ROOTSYS)"
> > >
> > > and use it instead of ROOTSYS.
> > > Since ROOTPATH is quoted this may not have confused any Windows
(or
> > > UNIX:-) utility.
> > >
> > > I'd like to mention the 3-d approach should work for either UNIX
or
> > > Windows
> > > properly with no extra trick. The first and second would work but
they
> > > would have hidden the problem rather to cure it. The file names
with
> > > special symbols or/and blanks inside is to be quoted to be treated
> > > properly.
> > >
> > > Let me know which way you like and whether third case causes any
> > > troubles for you.
> > >
> > > Myself likes the third solution since it shows how the file name
with
> > > blanks are to be managed properly and doesn't rely on any special
file
> > > system feature (like generating two different namespaces for one
and
> the
> > > same file)
> > >
> > > Very likely these approaches should be mentioned somewhere on ROOT
Web
> > > site.
> > >
> > > My best regards, Valeri
> > >
> > > > -----Original Message-----
> > > > From: GENTIT Francois-Xavier DAPNIA
[mailto:GENTIT@dapnia.cea.fr]
> > > > Sent: Tuesday, November 12, 2002 2:59 AM
> > > > To: 'Faine, Valeri'
> > > > Subject: RE: [ROOT] Do not install ROOT in "Program Files"
> > > >
> > > > Dear Valeri,
> > > > Muster3, joined with this mail, is a kind of minimum "hello"
> > > program,
> > > > using ROOT, that I always try first just after having installed
ROOT
> > > on
> > > > the
> > > > PC of a colleague of me willing to work with ROOT. It uses a
> makefile
> > > and
> > > > this makefile contains $(ROOTSYS). When ROOT has been installed
in
> > > > c:\Program files, it seems that the ROOT library are not found
> because
> > > of
> > > > the blank character in Program files.
> > > >
> > > > François-Xavier Gentit
> > > > DAPNIA/SPP CEA Saclay
> > > > http://gentit.home.cern.ch/gentit/
> > > >
> > > >
> > > >
> > > > -----Message d'origine-----
> > > > De : Faine, Valeri [mailto:fine@bnl.gov]
> > > > Envoyé : vendredi 8 novembre 2002 16:53
> > > > À : GENTIT Francois-Xavier DAPNIA; roottalk@pcroot.cern.ch
> > > > Objet : RE: [ROOT] Do not install ROOT in "Program Files"
> > > >
> > > >
> > > > Hello François,
> > > > I am sorry. It sounds I misunderstood the problem missing your
> > > > ". . .one has problems after that with makefile. . ."
> > > >
> > > > Can you tell me how I can reproduce the problem?
> > > > Is it Win 9x?
> > > >
> > > > For the Win9x family the installation mentioned below introduced
one
> > > > extra environment variable, namely ROOTPATH along with ROOTSYS.
> > > > ROOTPATH is a "short version" of ROOTSYS, that can be used to
avoid
> > > the
> > > > confusion within any user Makefile.
> > > > Check you autoexec.bat file after installation to see ROOTSYS
and
> > > > ROOTPATH values.
> > > >
> > > > Thank you, Valeri
> > > >
> > > >
> > > > >
> > > > > Hello François,
> > > > > Try the installation from http://root.bnl.gov
> > > > > It will set any Windows environment properly for any directory
and
> > > any
> > > > > Windows platform (I hope, Let me know if there is still any
> > > problem).
> > > > > No extra user effort is required, just click there and reply
some
> > > > usual
> > > > > questions. ("Program Files" should be fine as well)
> > > > >
> > > > > To avoid the clash with other ROOT installation, please remove
it
> > > > first.
> > > > > Or make sure your PATH and/or autoexec.bat don't contain the
old
> > > ROOT
> > > > > directory.
> > > > >
> > > > > My best regards, Valeri
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: owner-roottalk@pcroot.cern.ch
> > > > > [mailto:owner-roottalk@pcroot.cern.ch]
> > > > > > On Behalf Of GENTIT Francois-Xavier DAPNIA
> > > > > > Sent: Friday, November 08, 2002 7:51 AM
> > > > > > To: 'roottalk@pcroot.cern.ch'
> > > > > > Subject: [ROOT] Do not install ROOT in "Program Files"
> > > > > >
> > > > > > Dear Rooters,
> > > > > > I had twice to help rooters [Benoit.Horeau@cea.fr, and
> > > > > > Patrick.Jarry@cern.ch] because of the following problem
> concerning
> > > > > ROOT on
> > > > > > Windows:
> > > > > > if ROOT is installed in the directory C:\Program Files, (
> which
> > > is
> > > > > > proposed by default ! ) one has problems after that with
> > > makefile,
> > > > > > because
> > > > > > of the blank character in "Program Files".
> > > > > > A warning should be given to users on the ROOT download
page,
> > > and
> > > > > you
> > > > > > should choose C:\ instead of C:\Program Files for the
default
> > > > > directory
> > > > > > proposed.
> > > > > > Thanks
> > > > > >
> > > > > > François-Xavier Gentit
> > > > > > DAPNIA/SPP CEA Saclay
> > > > > > http://gentit.home.cern.ch/gentit/
> > > >
> > >
> > >
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:51:18 MET