Am Mittwoch, den 16.05.2018, 13:48 -0400 schrieb Richard Kimberly Heck: > It seems to me that there are two kinds of issues. One is what (if > anything) we install, and the other is what happens after that. I > think > the "auto-install packages" feature of MiKTeX is great for people who > don't want to get their hands too dirty, and Uwe was always right > that > we should try our best to help those folks.
Well, there's texliveonfly for people wanting that: https://ctan.org/pkg/texliveonfly > The problem, to my mind, is > how this interacts with configure.py: Because of how we test for > packages, I think, when we configure the first time, MiKTeX installs > everything we test for. Which takes forever, and really doesn't make > that much sense. (Actually, there's a list of packages to install in > Packages.txt that's used to tell MiKTeX to install a bunch of stuff > before we configure, but what it does is install everything that > configure.py would install.) Maybe an option, then, would be to limit > this list to stuff that is needed for e.g. compiling the > documentation, > and figure out some way to avoid installing everything on > configuration. That's the point. This "feature" causes more problems that it helps. And our layouts are still cluttered with style and class requirements just for the sake of this doubtful thing. We should remove those as soon as we have switched to TeXLive. Jürgen
signature.asc
Description: This is a digitally signed message part
