similar to: Namespace Dependencies not required

I was trying to ByteCompile a package that I made. The package compiles successfully with byte compile set to FALSE. When I set ByteCompile to TRUE, I receive the following error message while doing R CMD INSTALL /usr/lib/R/bin/INSTALL: line 34: 9964 Done echo 'tools:::.install_packages()' 9965 Segmentation fault | R_DEFAULT_PACKAGES= LC_COLLATE=C "${R_HOME}/bin/R" $myArgs

Hi, I am working at adding namespace to my packages, carefully following the doc "Writing R extensions" and some threads on the web. However I cannot find clear explanation about how to best deal with the import or importFrom functions in the name space. To make it short: To declare dependencies in the description file either after Depends: (packages including functions that are

I'm still working to add namespace support to some of my packages. I've removed the 'Depends' line from the DESCRIPTION file, and created an appropriate NAMESPACE files. Strangely, whenever I use 'importFrom(package, function)' R CMD check generates "Namespace dependencies not required" warnings . Without the import statements, the warning does not occur, but

H, I was trying to ByteCompile a package that I made. The package compiles successfully with byte compile set to FALSE. When I set ByteCompile to TRUE, I receive the following error message while doing R CMD INSTALL /usr/lib/R/bin/INSTALL: line 34: 9964 Done echo 'tools:::.install_packages()' 9965 Segmentation fault | R_DEFAULT_PACKAGES= LC_COLLATE=C "${R_HOME}/bin/R" $myArgs

Hello, I try to set up namespaces for packages. It is fine for several of them, except one whose compilation fails (under Windows XP & R 2.0.0): ---------- Making package svViews ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and metadata Error in parse(file, n, text, prompt) : syntax error on line 21 Execution halted make[2]: *** [nmspace] Error 1 make[1]: ***

Dear all, It is my understanding that using 'importFrom' in the NAMESPACE of a package allows to avoid conflicts between different packages defining objects with identical names. However, I can still see conflicts while loading the package using 'library'. Here is a toy example, with a package 'foo' importing 'as.igraph' from the igraph package, and 'nj'

I'd like to importFrom(parallel, mccollect, mcparallel) but on Windows these are not exported because this if(tools:::.OStype() == "unix") { export(mccollect, mcparallel, mc.reset.stream, mcaffinity) } appears at src/library/parallel/NAMESPACE:6 of svn r61857. So should I be doing if (tools:::.OStype() == "unix") { importFrom(parallel, mccollect, mcparallel) }

Hi, I am currently involved in the development of two R-packages, pkg1 and pkg2. They should not be dependent on each other, as most users will only be interested in one of them. Still, I want pkg2 to provide one extra S3 method for three functions (fun1-3) in pkg1 for objects of a class defined in pkg2 (class2), for those users who actually have both packages installed. I think this

Hi R users, I am developing two packages. Each package uses some functions from the other package. Now when I define these dependencies in the NAMESPACE file (via importFrom(XXXX,function1,....)), i get this error (when building one package): cyclic namespace dependency detected when loading 'XXXXXX', already loading ?YYYYYYY?, ?XXXXXXXXX? Is there any way to prevent this error?

I am developing a package that imports some functions from another package. The imported package (qcc) does not have a namespace and this is causing problems with loading of my package, which has a namespace. Is there a workaround to allow loading the namespace-less package? I searched the archives and found a suggestion that the package should be included in the Depends list, but this has not

I'm trying to learn how to use namespaces, so I have created a small package with two functions. My NAMESPACE file is importFrom(survival, Surv) export(mlreg.fit, risksets) because 'mlreg.fit' uses 'Surv' from 'survival'. However I get * checking package dependencies ... WARNING Namespace dependencies not required: survival Why? (If I remove 'importFrom' I

Hi, I am a bit unsure about using imports in packages and have a few questions. I'm sure the answer to some of these is 'it depends', but I'm interested in what others think and 'best practices' when this is the case. 1) If I use an import or importFrom declaration in a NAMESPACE, should I also qualify the package in calls to the imported function (e.g.

Hello, I really need some insight on a problem we encountered using grid, lattice and gridExtra. I tried to reduce the problem, so the plot make no sense. we have a package: gridextrabug with: DESCRIPTION ------------------ Package: gridextrabug Title: gridextrabug Version: 0.1 Author: toto Maintainer: toto <karl.forner at quartzbio.com> Description: gridextrabug Imports: grid,

In > R.version.string [1] "R Under development (unstable) (2011-12-15 r57901)" section 1.6.6 of 'Writing R Extensions' says Note that exporting methods on a generic in the namespace will also export the generic, and exporting a generic in the namespace will also export its methods. and Note that importMethodsFrom will also import any generics defined in

>>>>> Adrian Du?a <dusa.adrian at unibuc.ro> >>>>> on Tue, 13 Mar 2018 09:17:08 +0200 writes: > On Mon, Mar 12, 2018 at 2:18 PM, Martin Maechler <maechler at stat.math.ethz.ch> > wrote: >> [...] >> Is that so? Not according to my reading of the 'Writing R >> Extensions' manual, nor according to

Dear R-help, Can some one tell me if it's possible to have conditional importFrom() in the package NAMESPACE file? Basically I'd like to know if it's possible to make the NAMESPACE file compatible with R 1.9.0 and those 1.8.1 and earlier. The problem is that I want to import cmdscale(), which is in `mva' prior to 1.9.0 but in `stats' post 1.9.0. Any pointer much appreciated!

On Mon, Mar 12, 2018 at 2:18 PM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > [...] > Is that so? Not according to my reading of the 'Writing R > Extensions' manual, nor according to what I have been doing in > all of my packages for ca. 2 years: > > The rule I have in my mind is > > 1) NAMESPACE Import(s|From) \ >

I have a revised version of the gregmisc package, which I've converted into a package bundle each of which has a namespace: gplots, gmodels, gdata, gtoools. Of course, there are interdependencies among these namespaces: gsun374: /tmp [11]> cd gregmisc/ gsun374: gregmisc [12]> grep import */NAMESPACE gdata/NAMESPACE:importFrom(gtools, odd, invalid, mixedsort)

Dear list, It seems that a package (pkgB) using another package (pkgA) with S4 generics formed by taking existing functions (for example 'plot') must not import the existing functions ('plot') in its namespace to avoid the warning "replacing previous import: plot". Suppose we use the simple 'import' directive in the name space of pkgB. pkgA and pkgB files would

>>>>> Adrian Du?a <dusa.adrian at unibuc.ro> >>>>> on Fri, 9 Mar 2018 10:34:30 +0200 writes: > Dear All, > I understand the R CMD checks with only the base package attached, > everything else (including the other packages bundled with the base R) > should be imported and most importantly declared in the Imports field from