Richard Kimberly Heck wrote: > 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. 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.
I don't really have much opinion about the particular solution if the installation occurs within minuttes... > While we're at this, it occurred to me that maybe a "devel" build would > be useful, too, that we could direct users to if they're having > problems, and we need more debugging info. Yes, that should be trivial if mingw build is functioning. Pavel
