----- Original Message -----
From: "Paul A. Rubin" <[EMAIL PROTECTED]>
To: <lyx-users@lists.lyx.org>
Sent: Monday, December 12, 2005 3:05 PM
Subject: Re: There's Something About Textclass.lst [WinXP, installing into]
Angus Leeming wrote:
Enrico Forestieri wrote:
Angus, what about a configure.bat script?
Y'know, sometimes the simplest ideas are the best ;-)
However, don't we need admin privileges to generate files in C:\Program
Files\LyX\Resources\lyx ?
Not positive, but I don't think so. Whomsoever shall create that
directory, yea verily shall he/she/it own it, and have all sorts of
permissions in it. I think (security on Windows has a stochastic
element). So if the batch file is run under the same login id that
installed the software, it should work. Maybe. (An administrator could
also run it.)
Paul
Well, we are talking about an ordinary user and they did not
create C:\program files, that is created during the initial install.
The initial install is where/when the admin password is created.
When I tested this with Nautilus, my toy test alterego, which
has standard user rights, I could not install LyX to
C:\program files\Lyx , an error message was generated with
every attempted file install.
I could install however, to C:\Lyx or E:\LyX with 1.3.6
(but earlier I wasn't able to install to the C:\ drive in one test)
I've read various developer opinion about why MS decided
to have a C:\Program files, instead of C:\programs or the
German C:\programme. Nearly everybody agrees that it was
either stupid or deliberate, with most thinking deliberate since
it causes problems with Linux ports. I think that at the least
the default LyX install should be C:\Lyx rather than adopting
Microsoft propaganda. Has anyone read of a solid reason for
MS creating C:\program files? They are trying to force a habit.
The instructions that come with Miktex say to install to a
directory without spaces, and that is the default.
Likewise, I don't think runas.exe works unless you have the
admin or maybe high authority user status, just like su. An
ordinary user cannot use it. If you can use it, you already
own sufficient permissions. There is going to be no security
breach that obvious. I have installed LyX 1.3.7pre5 into
C:\LyX and C:\program files\Lyx and either way, one still
needs to run sh.exe configure. I also installed 1.3.7pre5
as Nautilus, an ordinary user. It would not install on the
C: drive. It would install on E:\LyX and sh.exe configure
also ran successfully, no admin rights needed. However,
it used python24 which I installed while acting as admin.
A current 137pre5 install can use python24 if it is already
installed, but I've read that a non-admin user can't install
python24(and maybe gsview) to start with, they have to
use Python23, which is no big deal.
So if the batch file is run under the same login id that
installed the software, it should work.
True enough, but the ordinary user can't install to
C:\program files to begin with, and maybe not to C:
although a batch file will work where you do manage
to install LyX. Curiously, the Lyx137 install on my
C: drive with admin priveleges was 30.31~mb but the
137pre5 install on the non-admin user, E: drive was
39.37mb~ So the tests seem to support Angus' view.
Regards,
Stephen
