[R-pkg-devel] A note from CRAN package check
Dear all, I notice that there is a note from CRAN package check results for our package as follows: Version: 1.4.1 Check: installed package size Result: NOTE installed size is 5.3Mb sub-directories of 1Mb or more: libs 5.2Mb The link to our package is here: https://cran.r-project.org/web/packages/FHDI/index.html So I know the problem is that our package exceeds the maximum size of 5MB. But I don't understand where we can trim our package to meet this requirement. We can not modify the source codes (C++ file and R files) because we may lose some functionalities of the package. Do we have to trim R documents? Any suggestions? So many thanks. Best regards, Yicheng Yang [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] A note from CRAN package check
On 28/09/2020 11:10 a.m., Yicheng Yang wrote: Dear all, I notice that there is a note from CRAN package check results for our package as follows: Version: 1.4.1 Check: installed package size Result: NOTE installed size is 5.3Mb sub-directories of 1Mb or more: libs 5.2Mb The link to our package is here: https://cran.r-project.org/web/packages/FHDI/index.html So I know the problem is that our package exceeds the maximum size of 5MB. But I don't understand where we can trim our package to meet this requirement. We can not modify the source codes (C++ file and R files) because we may lose some functionalities of the package. Do we have to trim R documents? Any suggestions? Reducing documents isn't going to be enough: most of the problem is in libs. You should investigate whether the libs you need are provided by other packages, or (if you wrote them yourself), whether it's really true that you can't shrink them. You could consider splitting your package into two packages, if there are several libs. You could try to explain to CRAN why you need to use all that space. There are packages on CRAN that exceed the 5Mb limit. Finally, you could choose to distribute your package in some other way besides CRAN. Duncan Murdoch __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] force revdepcheck to use local version of a dependency
Hi, I am using package 'revdepcheck' to check reverse dependencies of a package and it works great. But now I have a scenario such that I wish it to use a local version of one of the dependencies of the checked package and am not able to find out how. Some context: Package A imports package B. Package A has many reverse dependencies. I wish to check if an update to package B will break some of the reverse dependencies of A and/or repair broken reverse dependencies of A. It is obvious to update B on CRAN but this may lead unnecessarily to a number of CRAN updates. Georgi Boshnakov [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] force revdepcheck to use local version of a dependency
On 28 September 2020 at 17:17, Georgi Boshnakov wrote: | I am using package 'revdepcheck' to check reverse dependencies of a package and it works great. But now I have a scenario such that I wish it to use a local version of one of the dependencies of the checked package and am not able to find out how. Altering the set of directories as showsn by .libPaths() ? This could be as easy as setting `R_LIBS_USER` or `R_LIBS_SITE` or calling .libPaths(). | Some context: Package A imports package B. Package A has many reverse dependencies. I wish to check if an update to package B will break some of the reverse dependencies of A and/or repair broken reverse dependencies of A. It is obvious to update B on CRAN but this may lead unnecessarily to a number of CRAN updates. We have similar issue with CI Runners, RHub, win-builder -- they may only see the fixed set of CRAN packages and versions, and/or system libraries. Plus, these days getting an update onto CRAN is no longer as simple as it used be (unless the package is small, in excellent health, and without many reverse depends itself). Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] force revdepcheck to use local version of a dependency
You can define the special dependency of the revdep-checked package in the `Remotes` field. More info: https://cran.rstudio.com/web/packages/remotes/vignettes/dependencies.html E.g. if you are revdep-checking package PKG, then you can add something like this in the DESCRIPTION file of PKG: Remotes: local::/path/to/your/package or if the package is on GitHub: Remotes: user/repo Then revdepcheck will automatically install the special version of the dependency, for the dev version of the revdep-checked package. (But not for the CRAN version of the package.) Best, Gabor On Mon, Sep 28, 2020 at 6:17 PM Georgi Boshnakov wrote: > > Hi, > > I am using package 'revdepcheck' to check reverse dependencies of a package > and it works great. But now I have a scenario such that I wish it to use a > local version of one of the dependencies of the checked package and am not > able to find out how. > > Some context: Package A imports package B. Package A has many reverse > dependencies. I wish to check if an update to package B will break some of > the reverse dependencies of A and/or repair broken reverse dependencies of A. > It is obvious to update B on CRAN but this may lead unnecessarily to a number > of CRAN updates. > > > Georgi Boshnakov > > > [[alternative HTML version deleted]] > > __ > 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
Re: [R-pkg-devel] force revdepcheck to use local version of a dependency
Thanks, adding remotes to DESCRIPTION did what I was after. For reference (including me), here is an outline of a possible workflow: 1. run revdep_check(), with many reverse dependencies something like revdep_check(num_workers = 4) speeds the things up dramatically. 2, if there are failures run revdep_add_broken() 3. bug-fix 4. run revdep_check() or revdep_check(num_workers = 4), Due to 2. Above, this will run only the checks that failed the previous time. Of course this assumes that the bug-fixes didn't break things that work. 5. repeat 2. - 4. Georgi Boshnakov -Original Message- From: Gábor Csárdi Sent: 28 September 2020 18:46 To: Georgi Boshnakov Cc: r-package-devel@r-project.org Subject: Re: [R-pkg-devel] force revdepcheck to use local version of a dependency You can define the special dependency of the revdep-checked package in the `Remotes` field. More info: https://cran.rstudio.com/web/packages/remotes/vignettes/dependencies.html E.g. if you are revdep-checking package PKG, then you can add something like this in the DESCRIPTION file of PKG: Remotes: local::/path/to/your/package or if the package is on GitHub: Remotes: user/repo Then revdepcheck will automatically install the special version of the dependency, for the dev version of the revdep-checked package. (But not for the CRAN version of the package.) Best, Gabor On Mon, Sep 28, 2020 at 6:17 PM Georgi Boshnakov wrote: > > Hi, > > I am using package 'revdepcheck' to check reverse dependencies of a package > and it works great. But now I have a scenario such that I wish it to use a > local version of one of the dependencies of the checked package and am not > able to find out how. > > Some context: Package A imports package B. Package A has many reverse > dependencies. I wish to check if an update to package B will break some of > the reverse dependencies of A and/or repair broken reverse dependencies of A. > It is obvious to update B on CRAN but this may lead unnecessarily to a number > of CRAN updates. > > > Georgi Boshnakov > > > [[alternative HTML version deleted]] > > __ > 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
Re: [R-pkg-devel] A note from CRAN package check
Indeed, in this case, the CRAN team will let is pass anyway. Best, Uwe Ligges On 28.09.2020 18:41, Duncan Murdoch wrote: On 28/09/2020 11:10 a.m., Yicheng Yang wrote: Dear all, I notice that there is a note from CRAN package check results for our package as follows: Version: 1.4.1 Check: installed package size Result: NOTE installed size is 5.3Mb sub-directories of 1Mb or more: libs 5.2Mb The link to our package is here: https://cran.r-project.org/web/packages/FHDI/index.html So I know the problem is that our package exceeds the maximum size of 5MB. But I don't understand where we can trim our package to meet this requirement. We can not modify the source codes (C++ file and R files) because we may lose some functionalities of the package. Do we have to trim R documents? Any suggestions? Reducing documents isn't going to be enough: most of the problem is in libs. You should investigate whether the libs you need are provided by other packages, or (if you wrote them yourself), whether it's really true that you can't shrink them. You could consider splitting your package into two packages, if there are several libs. You could try to explain to CRAN why you need to use all that space. There are packages on CRAN that exceed the 5Mb limit. Finally, you could choose to distribute your package in some other way besides CRAN. Duncan Murdoch __ 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
Re: [R-pkg-devel] A note from CRAN package check
Dear Uwe and Duncan, Thanks a lot for your patient explanations. Because this problem is not an urgent error now, we will try to minimize the libs in our package regarding your suggestions in the next updates for other reasons. If we still can not meet this requirement of package size in the next update, we may try to explain to the CRAN team why we actually need this space as you suggested. Have a nice day. Best regards, Yicheng Yang On Mon, Sep 28, 2020 at 4:34 PM Uwe Ligges wrote: > Indeed, in this case, the CRAN team will let is pass anyway. > > Best, > Uwe Ligges > > On 28.09.2020 18:41, Duncan Murdoch wrote: > > On 28/09/2020 11:10 a.m., Yicheng Yang wrote: > >> Dear all, > >> > >> I notice that there is a note from CRAN package check results for our > >> package as follows: > >> > >> Version: 1.4.1 > >> Check: installed package size > >> Result: NOTE > >> installed size is 5.3Mb > >> sub-directories of 1Mb or more: > >> libs 5.2Mb > >> > >> The link to our package is here: > >> https://cran.r-project.org/web/packages/FHDI/index.html > >> > >> So I know the problem is that our package exceeds the maximum size of > >> 5MB. > >> But I don't understand where we can trim our package to meet > >> this requirement. We can not modify the source codes (C++ file and R > >> files) > >> because we may lose some functionalities of the package. Do we have to > >> trim > >> R documents? Any suggestions? > > > > Reducing documents isn't going to be enough: most of the problem is in > > libs. > > > > You should investigate whether the libs you need are provided by other > > packages, or (if you wrote them yourself), whether it's really true that > > you can't shrink them. > > > > You could consider splitting your package into two packages, if there > > are several libs. > > > > You could try to explain to CRAN why you need to use all that space. > > There are packages on CRAN that exceed the 5Mb limit. > > > > Finally, you could choose to distribute your package in some other way > > besides CRAN. > > > > Duncan Murdoch > > > > __ > > R-package-devel@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
