----- Original Message ----- From: "Jean-Marc Lasgouttes" <[EMAIL PROTECTED]>
To: "Stephen Harris" <[EMAIL PROTECTED]>
Cc: "LyX Users" <lyx-users@lists.lyx.org>; "LyX Announce" <lyx-announce@lists.lyx.org>
Sent: Wednesday, January 18, 2006 1:56 AM
Subject: Re: LyX 1.3.7 is released with Windows lack of Documentation Textclass.lst error


"Stephen" == Stephen Harris <[EMAIL PROTECTED]> writes:

Stephen> Apparently this version of the Lyx Windows 1.3.7 release uses
Stephen> the Angus installer rather than the Uwe installer.

Uh? This version does not use any of the installers. The installers
are two different packagings of 1.3.7.


Perhaps I gave the impression I was talking about the 1.3.7bz2 file that a
user compiles on his system. I was talking about the downloadable binary.
Windows users tend to think of the .exe as the program, not the sources.

-------------------------------------------------------------

http://wiki.lyx.org/Windows/LyX137
"Download
LyX 1.3.7 for Windows is available via one of two installers.

* The official installer, provided by the LyX team, is relatively simple and
will install only LyX itself, although it provides links to much of the other software that LyX uses. If you're upgrading from an earlier version of LyX and already have MiKTeX, Perl, Python et al. installed on your machine,
you should use this.

* Uwe Stöhr has created a separate installer that packages up all of these extra bits and pieces too.
--------------------------------------------------------------

SH: So I meant the "official" installer although I think of that as the
official release for Windows because the developers seem to think so.
(Someone commented that he thought Uwe's installer a bit too complex.)
Apparently the official installer uses a later model lyx_configure.C than
the lyx_configure.C of the June, Uwe installer. I base that on the posts:
---------------------------------------------------------------

Uwe wrote: Btw. what are the changes in the lyx_configure.C from
today are for?

Angusreplied: They make it more robust. I've used it for the last several
LyX1.3.7preX releases.

UWe countered: "This isn't that robust:

You know that we have several user reports that the configuration script
doesn't start. I also get this error now with the new lyx_configure. My
installer uses the old one from june and I never had this problem. I'll
send you the old one, perhaps you have an idea what causes the problem."

------------------------------------------------------

Angus Leeming schrieb:
"LangString FinishPageMessage "${LYX_LANG}" "LyX should now be installed. However, some of our users report that the configure script fails to run and, as a result, LyX fails to start, reporting a missing textclass.lst file. To fix, run the command: 'sh configure' from the LyX/Resources/lyx directory." [SH: This is why I expected to see a warning.]

Uwe responded:
"I don't think it is good to inform the user about this problem. Most users
will definetively be confused by this complicated message. (Average Win
users don't know what "sh configure" means.) How often does this problem
appear so that is that important to inform _every_ user this way?"

-------------------------------------------------------------------------

Stephen> The result is that on several machines the Angus installer
Stephen> fails to complete because it does not run the configure
Stephen> script and consequently no textclass.lst.

This is indeed annoying. I have plans to get rid of the problem by
removing the need to configure LyX at install time.


SH: It doesn't seem to me that Uwe's reasoning is consistent. As you
can guess I experience this problem and was expecting a warning at
the end of the install, or at least a mild warning on the LyX137 Wiki.
The first time it happened I was quite surprised.

This textclass.lst problem behavior didn't happen on my machine
when I built Lyx1.4.0pre3 using Mingw. Since it takes about six
hours to build this from sources, I'm in favor of the binary even if
it requires "sh configure". Like most Windows users, I just ignore
advice on how to fix gotchas unless it happens to me, but I don't
find the advice itself confusing. I changed the LyX137 Wiki to reflect
this textclass.lst failure possibility but my entry is easy enough to delete.

JMarc


Thanks for your input,
Stephen

Reply via email to