Re: [R-pkg-devel] Uncaught use of internal functions from other packages in R CMD check

2020-06-15 Thread Bert Gunter
Do note that ?asNamespace says: "Not **intended** to be called directly," (emphasis added) but not "should never be called directly" or some such. I don't know if this makes a difference to package checking, but it isn't clear to me that it would. Cheers, Bert Gunter "The trouble with having an

[R-pkg-devel] Uncaught use of internal functions from other packages in R CMD check

2020-06-15 Thread Balasubramanian Narasimhan
At least one package on CRAN uses get("foo", envir=asNamespace("imported_package")) and passes check. Is this known? -Naras __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Tomas Kalibera
On 6/15/20 6:52 PM, Duncan Murdoch wrote: On 15/06/2020 12:30 p.m., Daniel Kelley wrote: Duncan, thanks very much for that very helpful hint.  I got as follows.   My guess is that the first column in rdx$variables is an address offset, and so it seems that the lion's share of the storage is

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Daniel Kelley
I found as Duncan, but then I saw https://stackoverflow.com/questions/54144239/how-to-use-saverds-refhook-parameter and found more info as follows. (It will take me a while to go through the output, but basically I am seeing code from the "oce" package, which makes me think I ought to get rid

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Duncan Murdoch
On 15/06/2020 1:24 p.m., Ivan Krylov wrote: On Mon, 15 Jun 2020 12:52:20 -0400 Duncan Murdoch wrote: maybe someone else can suggest how to read an object from the .rdb file using R code. Internally R uses C code for this. This function seems to work for me: # filename: the .rdb file #

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Ivan Krylov
On Mon, 15 Jun 2020 12:52:20 -0400 Duncan Murdoch wrote: > maybe someone else can suggest how to read an object from > the .rdb file using R code. Internally R uses C code for this. This function seems to work for me: # filename: the .rdb file # offset, size: the pair of values from the .rdx

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Duncan Murdoch
On 15/06/2020 12:30 p.m., Daniel Kelley wrote: Duncan, thanks very much for that very helpful hint.  I got as follows.  My guess is that the first column in rdx$variables is an address offset, and so it seems that the lion's share of the storage is dedicated to items with names starting with

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-06-15 Thread Duncan Murdoch
On 15/06/2020 12:05 p.m., Martin Maechler wrote: Duncan Murdoch on Sun, 14 Jun 2020 07:28:03 -0400 writes: > I agree with almost everything you wrote, except one thing: this isn't > newly enforced, it has been enforced since the help system began. What > I think is new is

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Daniel Kelley
Duncan, thanks very much for that very helpful hint. I got as follows. My guess is that the first column in rdx$variables is an address offset, and so it seems that the lion's share of the storage is dedicated to items with names starting with a decimal point. For example, the "[[" item is

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-06-15 Thread Martin Maechler
> Duncan Murdoch on Sun, 14 Jun 2020 07:28:03 -0400 writes: > I agree with almost everything you wrote, except one thing: this isn't > newly enforced, it has been enforced since the help system began. What > I think is new is that there are now tests for it. Previously

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Ivan Krylov
On Mon, 15 Jun 2020 11:13:21 + Daniel Kelley wrote: > A possible clue is that I get a large-file note on macOS, but not > when I use rhub for test linux builds, or winbuilder for a windows > build. I do not have ready access to either linux or windows > machines, to examine those builds in

Re: [R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Duncan Murdoch
I can't install your package (I don't have an up to date GDAL), but maybe this is some help: - Package dependencies aren't included, except possibly for static linking of C/Fortran/C++ code. Those normally won't end up in an .rdb file. - .rdb files are part of the lazy load mechanism. You

[R-pkg-devel] how to prevent a small package from yielding a large installed size?

2020-06-15 Thread Daniel Kelley
I am working on a package (https://github.com/ArgoCanada/argoFloats) that has a 412K source tarball (most of which is data; the R code is 176K), but that creates a library .rdb file of MUCH larger size, namely 7.2M. This file causes a build NOTE, being over the threshold of 1M, and that