search for: check_package_cran_incom

...cking CRAN incoming feasibility ...Warning in url(sprintf("%s/src/contrib/PACKAGES.gz", u), "rb") : unable to resolve 'CRAN.R-project.org' NB: need Internet access to use CRAN incoming checks OK * checking package namespace information ... OK ... Looking at tools:::..check_package_CRAN_incoming() [in src/library/tools/R/QC.R], there are few places where different online URLs: URL 1: %s/src/contrib/PACKAGES.gz, URL 2: %s/src/contrib/Meta/archive.rds, URL 3: %s/src/contrib/Meta/current.rds, URL 4: %s/web/packages/packages.rds are downloaded, but it is only the first one that is downloa...

..., when I run R CMD check with flag --as-cran, the process hangs at stage: * checking CRAN incoming feasibility ... I am pretty sure it is a proxy issue. I looked at the check code in the tools package and it seems that the issue is in the local function `.repository_db()` (defined in `tools:::.check_package_CRAN_incoming()`), which eventually calls `url()` with argument open="rb", that hangs probably because it does not use the proxy settings. I had a similar issue with `source()`, which apparently uses internal network functions (not as download.file), but is supposed to work behind a proxy (corre...

Are there technical reasons that package names cannot be snake case? This seems to be enforced by `.standard_regexps()$valid_package_name` which currently returns "[[:alpha:]][[:alnum:].]*[[:alnum:]]" Is there any technical reason this couldn't be altered to accept `_` as well, e.g. "[[:alpha:]][[:alnum:]._]*[[:alnum:]]" I realize that historically `_` has not

...ceptable for 15+ years (since R 1.9.0 I > > believe). Might we also allow underscores for package names? > > The tarball names separate the package name from the version number > using an underscore. There is code that is written to assume there is > at most one underscore, e.g. .check_package_CRAN_incoming in > src/library/tools/R/QC.r. > > That code could be changed, but so could the proposed package name... > > Duncan Murdoch