Bo Peng wrote:
And here it is conclusion:
The configure.py script does not work correctly. My guess is that the
case where a class is missing and MikTex is configured to
download it, but it fails to do so, is not correctly treated, or not
treated at all, by the script.
configure.py works OK on all platforms other than windows/miktex
because of this automatic downloading problem. The problem is that
miktex does not report any error when it fails to download a package,
and configure.py can not do anything here (without big changes to the
package detection mechanism).
I have investigated this problem but have no proper solution at hand.
Another developer has contacted Miktex developers who would hopefully
fix this in the next release of miktex.
Cheers,
Bo
Bo,
This has no doubt been thrashed out by developers before, but is there
any reason why the config script can't just call kpsewhich for each
class to see if it's found. Granted that would not detect a defective
(corrupted) class file, but it seems as if it would be faster and less
painful in general. I confess here that I don't know if kpsewhich is
ubiquitous among LaTeX distros, or whether there are equivalents among
other distros.
/Paul
