> Surely the software just has to check that there is web connection to a CRAN mirror.
Nope! The full code is in tools:::.check_package_CRAN_incoming (the body of which filled up my entire console), but to name a few checks it has to do: check that the name of the package is not the same as any other, including archived packages (which means that it has to download the package metadata), make sure the licence is ok, see if the version number is ok. 10 minutes is quite a lot though. I suspect the initial connection may have been faulty. On Tue, 16 Jan 2024 at 16:15, Rolf Turner <rolftur...@posteo.net> wrote: > > > 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 ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
