Thanks duncan.
I fixed it by changing to depends and resubmitting my packages. But I
changed from depends to imports for a very specific reason. namespace
conflicts. There are work arounds for that so its not terminally
broken, but IMPORT had the promise of just the elegance I was looking
for.
On 23/09/2011 12:57 PM, steven mosher wrote:
Duncan
I have a related question.
I need one function from R.utils. But R.utils depends on R.oo and R.methodsS3.
so I made R.util an import and then used importFrom() in the namespace.
The package passed the "check". However when it came to use
Duncan
I have a related question.
I need one function from R.utils. But R.utils depends on R.oo and R.methodsS3.
so I made R.util an import and then used importFrom() in the namespace.
The package passed the "check". However when it came to use the function
it had not been loaded? do I need
On 11-09-19 4:48 PM, Stephanie M. Gogarten wrote:
I am trying to build a package (GWASTools, submitted to Bioconductor)
that uses the "sandwich" package. I have references to "sandwich" in
DESCRIPTION:
Imports: methods, DBI, RSQLite, sandwich, survival, DNAcopy
and NAMESPACE:
import(sandwich)
I am trying to build a package (GWASTools, submitted to Bioconductor)
that uses the "sandwich" package. I have references to "sandwich" in
DESCRIPTION:
Imports: methods, DBI, RSQLite, sandwich, survival, DNAcopy
and NAMESPACE:
import(sandwich)
In the code itself is a call to vcovHC:
Vhat <- v
