From ggrothendieck at gmail.com  Fri Dec  7 17:12:14 2007
From: ggrothendieck at gmail.com (Gabor Grothendieck)
Date: Fri, 7 Dec 2007 11:12:14 -0500
Subject: [Rd] Building packages
In-Reply-To: <47596FB0.7090904@lancaster.ac.uk>
References: <47596FB0.7090904@lancaster.ac.uk>
Message-ID: <971536df0712070812w69023d27k984d7eb86aa2039@mail.gmail.com>

An svn checkout directory can contain a mix of files that
are mirrored in the svn and not mirrored.  In particular, if you
add a new file into your checkout directory it will not automatically
go into the repository on your next commit unless you specifically
place that file under svn control so junk files remain local.

You can exclude files from R CMD build using the .Rbuildignore file.
See the Writing Extensions manual.

On Dec 7, 2007 11:07 AM, Barry Rowlingson <b.rowlingson at lancaster.ac.uk> wrote:
> I've started a new package and I'm trying to work out the best way to do
> it. I'm managing my package source directory with SVN, but "R CMD build"
> likes to dump things in the inst/doc directory when making vignette PDF
> files. I don't want to keep these in SVN (they aren't strictly
> 'source'), so it set me thinking.
>
> One of the other projects I work with has an out-of-source build system.
> You make a 'build' directory, run a config system (cmake-based) and then
> 'make' does everything in the build directory without touching the
> source tree. Very nice and neat. How much work would it take to have
> something similar for building R packages? At present I've just got some
> svn:ignore settings to stop SVN bothering me.
>
>  I also hit the problem of vignettes needing the package to be
> installed before being able to build them, but not being able to install
> the package because the vignettes wouldn't build without the package
> already being installed. The fix is to build with --no-vignettes, then
> install the package, then build with the vignettes enabled. Seems
> kludgy, plus it means that vignettes are always built with the currently
> installed package and not the currently-being-installed package. So I
> install and do a second pass to get it all right again.
>
>  Or am I doing it wrong?
>
>  Once I get smooth running of R package development and SVN I might
> write it up for R-newsletter - there's a couple of other tricks I've had
> to employ...
>
> Barry
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>



[Rd] Building packages
Gabor Grothendieck