Peter,

This is a relatively "new" warning from R CMD check (for some definition of
new).  The authors of Hmisc have clearly not yet gone through the process
of cleaning it up, as you are doing right now (and there are many other
packages that still need to address this, including several of mine).
 Given who the authors are of Hmisc, I would suggest writing to them and
ask them to look into this, and ask for a time estimate.

In the meantime, you may have to do something about this, and whatever you
do I would suggest following the Hmisc package and undo it as soon as
possible, as the right thing is to fix Hmisc.  Having said that, it is not
clear to me that you can easily solve this yourself, because I don't think
that putting survival into your own imports will make the package available
to Hmisc functions, but it is not impossible there is some way around it.

Best,
Kasper




On Fri, Sep 27, 2013 at 11:04 PM, Peter Langfelder <
peter.langfelder@gmail.com> wrote:

> Hi all,
>
> one of my packages uses the rcorr.cens function from the Hmisc
> package. Until now I have simply put the Hmisc package into Depends:,
> but prodded on by new CRAN requirements, I tried to moving it into
> Imports:. However, this fails because rcorr.cens calls the function
> is.Surv from survival, which does not seem to be on the search path
> when Hmisc is "imported from" rather then being "depended on". (Hmisc
> both Depends: on and Imports: from survival, which is a bit confusing
> and discouraged by Writing R extensions.)
>
> Do I need to include an explicit dependency on or import from
> survival? Or should I leave Hmisc in the "Depends: " field? Apologies
> if this is a trivial question - I am not versed in R internals and
> couldn't find the answer in the Writing R extensions manual either.
>
> Thanks,
>
> Peter
>
> ______________________________________________
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

	[[alternative HTML version deleted]]

