similar to: Ah I've got it now .Thanks! RE: Understanding why "no metadata object found ... not exported?" warnings from the methods package exist, and what they mean

On looking more closely, the purpose of finding the class definition is to update the entry for the new relationship, as the warning message suggests. That requires that the namespace holding the definition be writable. In the case of subclass information, the original namespace is very likely to be locked, if it's not the package currently being loaded. Copying the definition in order to

This warning message is on my to-look-at list; I agree that sometimes it's obviously possible for the system to get the information if it tries hard enough. The message means what it says: Class information in a session includes the currently loaded subclasses of a particular class. Not critical but sometimes useful. In this case, (as I understand it without having looked recently), the

Hi I am seeking to understand why the methods package (to be specific `methods:::.findOrCopyClass` when called by `setIs` when called by `setClass`) emits a warning message such as ` class "SpatialLinesNULL" is defined (with package slot 'rgeos') but no metadata object found to revise subclass information---not exported? Making a copy in package 'minweSpatialNULL `

I think that this problem is actually more general than just ABI versioning. The common definition of ABI refers to compiled code, but with R packages similar problems might happen (and they to happen) without any compiled code. I think the key issue is the concept of build-time dependencies. While R packages usually does not distinguish between build-time and run-time dependencies, they still do

I figured it out, at least enough to get rgeos's gSimplify function to work, which was my original goal; the stringr problem was with 0.2, however I got stringr 0.5 to install by changing the minimum version in DESCRIPTION from R2.11 to R 2.10. ... Thanks for the help! ############# # This is how I got rgeos to install in R GUI on my Intel Mac OS X 10.4: ############# # stringr

Hello Everybody. i am installing rgeo in R-2.13 on debian lenny. i am getting following error. Can anybody help me why i m not able to compile rgeos. rgeos_misc.c: In function ‘rgeos_hausdorffdistance’: rgeos_misc.c:55: error: ‘GEOSHausdorffDistance_r’ undeclared (first use in this function) rgeos_misc.c:55: error: (Each undeclared identifier is reported only once rgeos_misc.c:55: error: for

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

Some notes on installing rgeos in R 2.14.0 on a Linux Mint 11 (x86_64-pc-linux-gnu) machine 1. rgeos 0.1-15 will not run with GEOS 3.2.0-1, which is the version currently available on Synaptic package manager 2. I installed GEOS 3.3.1 (the latest version) from http://trac.osgeo.org/geos/, but rgeos will not run with this either 3. I then install GEOS 3.2.3, and now rgeos works fine! It seems

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 ...

While installing software on a new computer, I thought I would try to use Cygwin to build an R package. (Note: NOT Ripley/Murdoch's Rtools). I uncovered and solved two issues, one of which appears to be identical to a problem previously reported (and unsolved) on this list. I offer this information in case it will be helpful. (1) Cygwin defaults to UNIX mode when installed, but it appears

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) > >

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

Jun hi again! Sorry for bothering. Although I had no problem with building Windows package under Linux, I noticed that man pages are not processed as they should or maybe I have a problem with my setup. My package is called 'GeneticsPed'. Instead of HTML or text files I just got a GeneticsPed.Rd.gz in man directory of a package (this is within GeneticsPed_0.1.zip file!). The file

Hi all, I''m struggling with the following: I have a defined type wrapped in a class: class myclass { define mytype(bla) { file { "blabla": .... } exec { "blablabla": ... } } } And I access the defined type in my other class by doing this: class otherclass { include myclass myclass::mytype { "alb": ... } # and here I want to

Dear list, I've a package, myPkg, which was developed on R v 2.6.1. I have installed R v2.9.2 from source, with a shared library and tcktk support. The package, myPkg, depends on RSPerl, and imports it in its NAMESPACE. I've downloaded and installed RSPerl using command: >R CMD INSTALL -c --configure-args="--with-modules='IO \ Fcntl Socket Storable XML::Parser::Expat

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 would like to be able to load two versions of a package at once and to do that was thinking of giving each version a different package name in the DESCRIPTION file and the building and installing each such version separately. library(myPkg1) library(myPkg2) and then use myPkg1::myFun() and myPkg2::myFun(). To do that easily it would be convenient if one could change the package name in only

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