Am Di., 9. Juni 2020 um 13:12 Uhr schrieb Jean-Marc Lasgouttes < [email protected]>:
> We have to discuss whether running configure.py is necessary at > installation time. AFAIR, this is just a trick to make miktex install > all missing LaTeX packages (see the chkconfig.ltx part). > > Is there any other use for doing it? > Actually, if the user runs the installer as admin, then the packages will be installed as admin (in case the auto install for packages is allowed in MiKTeX preferences), which would not be the case if the installer wouldn't run configure.py and the user starts LyX after installation as user. So in this case it is worth running configure.py from the installer. In other cases it doesn't hurt too. Therefore I'd say we keep that functionality. Am Di., 9. Juni 2020 um 13:14 Uhr schrieb Jürgen Spitzmüller <[email protected] >: > Am Dienstag, den 09.06.2020, 12:26 +0200 schrieb Yu Jin: > > Well actually I have found the issue here, the files, which we see > > there are supposed to be in the user dir > > (C:\Users\username\AppData\Roaming\LyX2.3), they are created by > > configure.py. I have found the issue here, looks like the official > > installer has a bug there and I have coded that bug too simply > > because I did not know (just in another folder). Fix is attached, > > please commit (message can be e.g.: Run configure.py in the user dir) > > Done. > Thanks, should I build new betainstallers? The current ones might fail deleting install dir while uninstalling. Also please find attached this fix for the official installer, please commit and backport.
RunConfigureInUserdirOficial.diff
Description: Binary data
-- lyx-devel mailing list [email protected] http://lists.lyx.org/mailman/listinfo/lyx-devel
