From maechler at stat.math.ethz.ch  Fri Dec  1 11:51:59 2006
From: maechler at stat.math.ethz.ch (Martin Maechler)
Date: Fri, 1 Dec 2006 11:51:59 +0100
Subject: [Rd] R CMD check warning about boot ?
In-Reply-To: <17774.58742.482456.68184@basebud.nulle.part>
References: <17774.1882.621732.219274@basebud.nulle.part>
	<456EA128.6050805@statistik.uni-dortmund.de>
	<17774.49793.503972.781158@mithrandir.hornik.net>
	<17774.58742.482456.68184@basebud.nulle.part>
Message-ID: <17776.2383.700920.192129@stat.math.ethz.ch>

>>>>> "Dirk" == Dirk Eddelbuettel <edd at debian.org>
>>>>>     on Thu, 30 Nov 2006 08:06:46 -0600 writes:

	  [.............]

    Dirk> The boot package loads fine, and is current.  Why does
    Dirk> R CMD check think it is an error that boot happens to
    Dirk> live in a particular directory, for as long as that
    Dirk> directory is known to .libPaths() ?

There's quite a difference between 
.libPaths()  in interactive and in "R CMD check" use :

'R CMD check' does not use your R_ENVIRON where you probably set
your R_LIBS .
I vaguely remember that there a good reasons for this behavior,
but I don't recall them at the moment.

My solution (or "workaround the design bug"?) has been - for
packages I develop - to have small helper scripts that basically do

  R_LIBS=<the_non_standard_libs_I_need>  R CMD check <options>  <mypackage>

Martin



[Rd] R CMD check warning about boot ?
Martin Maechler