search for: somepkg

...nce the other package has done so. But my namespace is locked by the time this occurs. Can someone either tell me how to do this, suggest a better alternative, or point me to another package that does something similar? Current attempt is something like the following: setHook(packageEvent("somepkg", "attach"), function(...) { cat("* Register", sQuote("oldstyle"), "as S3 class", "\n") setOldClass(c("oldstyle", "data.frame"), where = asNam...

Hi, I'm hoping to get some clarification of the intent of some of directives used in NAMESPACE files. 1. Is import(somePkg) also intended to import all classes and methods that are exported via exportClasses and exportMethods in somePkg? I think import pulls in classes and methods, but it isn't clear from the docs whether this is as intended. 2. What is exportMethods intended to do? I'm confused abou...

...dows / macOS as well. writeLines(gpg::gpg_sign("MD5"), "MD5.gpg") Attached is an example implementation of the latter (also available at https://git.io/vPb9G) which has been tested with several versions of GnuPG. It exposes an optional flag for CMD build, i.e: R CMD build somepkg --sign R CMD build somepkg --sign=jeroen.ooms at stat.ucla.edu The --sign flag creates a signature for the MD5 file [1] in the source package and saves it as MD5.gpg (similar to a Debian 'Release.gpg' file [2]). Obviously the package author or build server needs to have a suitable privat...

...(gpg::gpg_sign("MD5"), "MD5.gpg") > > Attached is an example implementation of the latter (also available > at > https://git.io/vPb9G) which has been tested with several versions of > GnuPG. It exposes an optional flag for CMD build, i.e: > > ? R CMD build somepkg --sign > ? R CMD build somepkg --sign=jeroen.ooms at stat.ucla.edu > > The --sign flag creates a signature for the MD5 file [1] in the > source > package and saves it as MD5.gpg (similar to a Debian 'Release.gpg' > file [2]). Obviously the package author or build server n...

...d, R has the mailing list, which is really simple, but: a) I found it really difficult at first to understand how it worked. b) I feel it does not fully respect the privacy of the package maintainers. c) And it can give place to e-mail Spam. In fact, Rstudio has disabled bug.report(package = "somePkg") command in order to avoid misuse. That is why I would suggest that, being JIRA free for Open Source Projects such as R: https://de.atlassian.com/software/views/open-source-license-request It would be really worth it to start using this modern platform gradually instead of Bugzilla, or the...

...e are several packages that by default perform multi-threaded processing using native code, but I'm not sure there's a way for such package to avoid running in multi-threaded mode if running in a forked child R processes. Imagine y <- parallel::mclapply(1:10, FUN = function(i) { somepkg::threaded_calculation_using_all_cores() }) where the developer of `somepkg` is off no control whether user calls it via mclapply() or via lapply(). I can see how the user of mclapply() / lapply() can pass on this information, but that's not safe and it might not be that the user is aware t...

...t, which is really simple, but: > a) I found it really difficult at first to understand how it worked. > b) I feel it does not fully respect the privacy of the package maintainers. > c) And it can give place to e-mail Spam. > > In fact, Rstudio has disabled bug.report(package = "somePkg") command in order to avoid misuse. > > That is why I would suggest that, being JIRA free for Open Source Projects such as R: > > https://de.atlassian.com/software/views/open-source-license-request > > It would be really worth it to start using this modern platform gradually...

...36.html but it doesn't seem to be related (at least not in an obvious way) to the problems described in that previous thread. So the problem is that, with recent versions of R 2.12 (i.e. current R-alpha but I've observed this with R-devel for at least 2-3 months now), 'R CMD build <somepkg>' on Windows will fail on a random set of Bioconductor packages because of a tar problem. For example: R/bin/R.exe CMD build OLIN * checking for file 'OLIN/DESCRIPTION' ... OK * preparing 'OLIN': * checking DESCRIPTION meta-information ... OK /cygdrive/c/RTOOL...

Hello, All: tools::package_dependencies('Ecfun') failed to find how my development version of Ecfun was using rJava, which generated errors in "R CMD build Ecfun". This is because package_dependencies by default uses CRAN and ignores locally installed packages. What do you think about having this function check both locally installed and CRAN versions? It can