Am 11.03.2018 um 00:57 schrieb Scott Kostyshak:

If in the LyX 2.3.0 installer we provide an informative dialog, the user
might say "oh I did not know that LyX needed to update MiKTeX. I will
not install LyX now because I need to submit my paper tomorrow. After I
submit my paper, I can deal with an updated MiKTeX and fix any problems
that come from updated LaTeX packages so I will install LyX 2.3.0 at
that time".

Why do you claim that an update of MiKTeX's package handling introduces problems with LaTeX packages? I run all LyX files I have on my disc with the LyX 2.3.0 and don't get any compilation error.
I already wrote that I don't like these claims.

Why do you come up with such constructed examples? The use case of an installer is to install. However:

- If I have to submit a paper tomorrow I will fur sure not upgrade the software. For Word or LibreOffice you won't do this as well. - Even if you decided to install LyX 2.3.0 you made a decision - you want to have LyX. And with the installer you get it. - You expect people to have a lot of background knowledge and that they understand English well. Both is not the case for many if not most users. I also don't like that I have to issue the dialog with the OK button because not everybody will understand what this means since "MiKTeX" or "package" are not common for many users. Moreover the dialog is only in English. I decided to pop it up because an update can take several minutes (for example if you run the last update a year ago or never run an update) and if people think nothing is happening they might close the installer during the update process. The installer for 2.3.1 will of course return to the old installer behavior.

Allow me to continue your constructed case: The user denies any update and therefore don't get LyX 2.3.0. But he maybe reconfigure LyX 2.2.x and as result he cannot compile his document because LaTeX got broken. If he runs my LyX 2.3.0 installer he can afterwards also reconfigure his LyX 2.2.x without risking anything.

regards Uwe

Reply via email to