From murdoch at stats.uwo.ca  Wed Nov 17 22:19:07 2004
From: murdoch at stats.uwo.ca (Duncan Murdoch)
Date: Wed Nov 17 22:19:14 2004
Subject: [Rd] Building Packages on Windows using .Rbuildignore
In-Reply-To: <loom.20041117T213214-532@post.gmane.org>
References: <loom.20041117T190158-839@post.gmane.org>
	<6r7np0lfgogaq3b352qp2knd67c1r1bup5@4ax.com>
	<loom.20041117T213214-532@post.gmane.org>
Message-ID: <fofnp05f7gl9lqt63i5f8dtiodpoo9qnh0@4ax.com>

On Wed, 17 Nov 2004 20:44:48 +0000 (UTC), Gabor Grothendieck
<ggrothendieck@myway.com> wrote :

>If one does not use .Rbuildignore then with a pure R package
>one can run off the original source files, in this case
>in /wherever/mypkg, like this:
>...without .Rbuildignore ...
>R CMD install /wherever/mypkg
>R CMD check /wherever/mypkg
>R CMD build /wherever/mypkg
>R CMD build /wherever/mypkg --binary
>
>but if one DOES use .Rbuildignore then one must first build the
>package to remove the .Rbuildignore cited files and then run off
>the built files which were created by unpacking the tar.gz file.

... or what happens?  I still don't know exactly what you are claiming
goes wrong.  

It might be that the behaviour should be changed, or maybe there's an
existing workaround, but I'd like to see a clear statement of the
problem first.

Duncan Murdoch


[Rd] Building Packages on Windows using .Rbuildignore
Duncan Murdoch