search for: otherpkgs

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

On 16/12/2016 12:35 PM, Karl Millar wrote: > A couple of points: > - rebuilding dependent packages is needed if there is an ABI change, > not just an API change. For packages like Rcpp which export inline > functions or macros that might have changed, this is potentially any > change to existing functions, but for packages like Matrix, it isn't > really an issue at all

I'm trying to keep debugging of a development package relatively sane. I see that some packages manage to incorporate what appears to be Subversion (SVN) revision information in the package description; for example, > library(MASS) > sessionInfo()$otherPkgs$MASS$Revision [1] "$Rev: 3016 $" which looks like an auto-generated revision number. On the other hand, the rgl package (for example) appears to manually encode the SVN revision in the package number: > library(rgl) > sessionInfo()$otherPkgs$rgl$Version [1] "0.92.829&quo...

...geDescription) if (length(package) == 0) stop("no valid packages were specified") basePkgs <- sapply(pkgDesc, function(x) !is.null(x$Priority) && x$Priority == "base") z$basePkgs <- package[basePkgs] if (any(!basePkgs)) { z$otherPkgs <- pkgDesc[!basePkgs] names(z$otherPkgs) <- package[!basePkgs] } loadedOnly <- loadedNamespaces() loadedOnly <- loadedOnly[!(loadedOnly %in% package)] if (length(loadedOnly)) { names(loadedOnly) <- loadedOnly pkgDesc <- c(pkgDesc, lapply(loa...

Ah, I've got it now. >From `?base:bindenv` comes > " The namespace environments of packages with namespaces are locked when loaded." A locked environment > " prevents adding or removing variable bindings from the environment. Changing the value of a variable is still possible unless the binding has been locked" A bit of experimentation shows that as well as

When loading a package with library(APkg) or require(APkg) I would like to make sure that (1) the correct version of [R] is installed. If not an informative error message should be given. I would also like to make sure that (2) another required package which is loaded from within the APkg package (by require(OtherPkg)) is of a certain version or later. First of all, I believe that the check

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

Hi, Two easy questions I'm sure. 1) As an example if I use the code require(zoo) then once it's loaded is there a command that lists everything that zoo provides so that I can study the package? Certainly help(zoo) gives me some clues about what zoo does but I'd like a list. Maybe there's a way to query something but in Rgui under Win Vista ls() returns nothing after zoo

Hi, after updating R 2.5.0 devel yesterday we today observed many new unexpected failures in our daily package build and test system runs, which can be traced to recent changes in the implementation in try() (as noted in NEWS). Investigating this new implementation I come across an issue in conjuntion with using S4 classes and methods. try(expr) does not return an object with attribute