similar to: declare and validate options

On 29/03/2024 10:52 a.m., Antoine Fabri wrote: > Dear r-devel, > > options() are basically global variables and they come with several issues: > * they're not really truly owned by a package aside from loose naming > conventions > * they're not validated > * their documentation is not standard, and they're often not documented at > all, it's hard to know

> > I think there are too many packages that would need changes under this > scheme. There would be zero if the registration of options is not required for packages first uploaded on CRAN before the feature is implemented. If an option is not registered no validation is triggered and nothing breaks even if we opt in the behavior. > If those functions could be made simple enough and

Full_Name: David O. Nelson Version: 1.4.1 OS: solaris 2.7 Submission from: (NULL) (128.115.150.74) Putting patterns in .Rbuildignore has no effect when the tar being used is gnu tar (1.13) on solaris 2.7, whilst /usr/sbin/tar works perfectly. TO REPRODUCE: The current directory contains a source package directory ./mypkg... bimini.jgi-psf.org% echo >mypkg/foo bimini.jgi-psf.org% echo

Hi, my name is Paula. Im trying to learn how to build an R package in Windows XP using a simple example which includes a C source code. The foo.c file is located in mypkg/src/foo.c. I used the command Rcmd build --force --binary [pkgpath]. The problem is when I install the zip file in R the function foo doesn?t exist. The result a recieved during the building process is copied below. I really

Hi R Gurus! I'm trying to create a test package using the package.skeleton function. I wanted to add some compiled code too. In the src library, I put together a baby subroutine, compiled it and created a test.dll When I use the R cmd build, it works fine. But I get into trouble with the R CMD check section. /home/Desktop/R-2.5.1/bin # ./R CMD check mypkg * checking for working latex ...

I'm having a very hard time making R CMD check produce a clean check on examples because of the timings inserted into examples by R CMD check. I am getting a difference on every example output caused by timing information being inserted by 'R CMD check'. The current 'Writing R Extensions' manual[1] states on p. 14: If directory tests has a subdirectory Examples

Hello useRs I am trying to build a package for personal use and for making easier working with other people but I keep getting the same error message about the DESCRIPTION file not existing. when trying to install from a source tar.gz file: Error in .read_description(dfile) : file 'C:/Users/Propriétaire/AppData/Local/Temp/RtmpHFMONb/R.INSTALL647a3535/mypkg/DESCRIPTION' does not

Hi: I'm trying to create a package to pass to someone else to use a group of functions with help files. I'm working on Windows XP. Step One: I use the example > ## two functions and two "data sets" : > f <- function(x,y) x+y > g <- function(x,y) x-y > d <- data.frame(a=1, b=2) > e <- rnorm(1000) > >

Dear friends, I am writing a package that I think may be of interest to many people so I am in the process to build-check-write-thedocumentation for it. I have some questions regarding the "rules" that a package should abide in order to be consistent with the other packages on CRAN. I have read and reread the Writing R extension manual and googled the mailing list and I have found

Greetings: I've installed Rtools, MikTeX, perl, minGW, and HTML Help Workshop, and have succeeded in making, checking (using R CMD check mypkg) then building the simple example package.skeleton(list=c("f","g","d","e"), name="mypkg") R CMD build mypkg produces a tarball. I don't know how to get a zip file. But when I try to Install

Hi, 'R CMD INSTALL mypkg' and 'install.packages(mypkg, repos=NULL)' don't update mypkg help pages when mypkg is a source directory. They only install new help pages if there are some but they leave the already installed pages untouched. So you end up with mixed man pages from different versions of the package :-/ I found no mention of this in 'R CMD INSTALL --help' or

I am building a package say mypkg. Five months ago, when I built the package I got the mypkg manual in pdf format. Today, after making updates, I build the same package, same name, and steps; unfortunately I do not get the manual in pdf format. Rather I get the following message: cd: can't cd to /cygdrive/c/Documents saving output to 'mypkg-manual.pdf' ...Done Could any one

----- Forwarded by Ajay DAS/US/BMNA01 on 05/19/2008 03:11 PM ----- Ajay DAS To: r-help

Hi all, I was playing with R-devel 2005-03-08 on winXP Pro (installed from Duncan's installer). My .Rprofile contains: options(defaultPackages=c(getOption("defaultPackages"), "mypkg"), chmhelp=TRUE) but "mypkg" has not yet been installed in the library/ directory of this installation. When Rgui starts, I do not get any error or warning, but upon

It often happens that I submit a new revision of a package, say mypkg-1.0-10, from R-Forge to CRAN after running R CMD check locally and looking at the log files on R-Forge. But R-Forge has the devel checks disabled, and I get an email from CRAN pointing out some new warning or note I'm asked to correct. OK, I correct this and commit a new rev to R-Forge. But, is it still required to

Hi, I made a package on a linux box. All worked fine. The package contains only R code (no C). I then wanted to make a zip file so that I could test the package on a windows machine. I have tried all the obvious ways to do this (and even some that are not!), but to no avail. The only instructions I find about building packages for windows (e.g. mypkg.zip) seem to imply that the build be done

I noticed that in "R version 2.4.0 alpha (2006-09-16 r39365)" on Windows XP that I get this error: C:\Rpkgs>Rcmd install mypkg no Perl script 'install' The same command worked with no error in 2.3.1pat. If I capitalize INSTALL it does work; however, this was not necessary previously. Note that C:\Rpkgs>Rcmd check mypkg unlike install, still works in either lower or

Hi, Wouldn't it be awesome if package.skeleton() could be used to produce, well... a package skeleton? In a fresh R session: > package.skeleton("mypkg") Error in !have : invalid argument type This (not very informative) error message seems to occur because I'm trying to create a skeleton with no flesh on it: > foo <- function() {} >

dear R user, I al rying to compile an R package with some C code. everithing work fine as long as I work in Linux or MaCOX. unluckyly I can cant compile it under Windows, here is the error, but I cant figure it out what is the problem. can you help me? * using log directory 'C://MyPKG.Rcheck' * using ARGUMENT ' ' __ignored__ R version 2.11.0 (2010-04-22) * using session ARGUMENT

The package I'm working on can extract data from external packages but would otherwise have no dependency on them. However, I desire to be able to dispatch based on an external S3 class if its package is attached (.First.lib). My code is S4-based and its package has NAMESPACE. Registering the external class prior to the other package being attached doesn't seem to work so I am attempting