On Tue, Jun 09, 2020 at 07:15:22PM +0200, Yu Jin wrote: > Am Di., 9. Juni 2020 um 17:55 Uhr schrieb Enrico Forestieri <[email protected] > >: > > > On Tue, Jun 09, 2020 at 03:29:29PM +0200, Yu Jin wrote: > > > Am Di., 9. Juni 2020 um 14:21 Uhr schrieb Jean-Marc Lasgouttes < > > > [email protected]>: > > > > OTOH, for texlive, running configure.py is just wasting time if I > > > > understand correctly. And since a lot of packages are checked in > > > > configure.py just for this, we are talking about a lot of time, here. > > > > > > > > > > I see, but don't we then save this time when LyX is started for the first > > > time? Otherwise configure.py would run there. > > > > I don't think so, because configure.py is run for the admin user at > > installation time. It will be run again when lyx is started by another > > user. > > > Agree for this case. > > > > Then, there is also the issue that, before running configure.py, the > > installer subverts the MikTeX settings by allowing to always install > > packages on the fly, irrespective of the choice made through the > > MikTeX console. > > > Are you sure? I have neither experienced this nor found anything related to > this in the NSIS code. Maybe this was the case with the bundle installer?
Yes, I am sure. I have always been scared by that and didn't use the installer for years. I tried it again when it was built by Riki, but it was still like that. After using the installer I spent almost an hour finding and uninstalling a lot of packages I never use. However, that was with lyx 2.3.3 and I never used it again thereafter, so maybe it is not like that anymore. -- Enrico -- lyx-devel mailing list [email protected] http://lists.lyx.org/mailman/listinfo/lyx-devel
