This post essentially amounts to idle curiosity. I don't really expect that anything can be done about the problem that I perceive.
When I check a package using --as-cran, the code spits out a line checking CRAN incoming feasibility ... and then disappears into a black hole for what seems an eternity (5 or 10 minutes). Why does this step take so long? Surely the software just has to check that there is web connection to a CRAN mirror. I would have thought that this would be executed virtually instantaneously. cheers, Rolf Turner -- Honorary Research Fellow Department of Statistics University of Auckland Stats. Dep't. (secretaries) phone: +64-9-373-7599 ext. 89622 Home phone: +64-9-480-4619 ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel