Gabor Grothendieck schrieb:
On Fri, Oct 10, 2008 at 7:06 PM, Peter Ruckdeschel
[EMAIL PROTECTED] wrote:
[snip]
This could indeed be an option, but as noted in my reply to Robert, my
guess is that in the library where you install your packages to and which is
found with system.file(), you
Hi,
this may be slightly off-topic, but as you are the experts:
we have written a small vignette, in which we want to refer to
.R, .Rd source files by means of relative paths.
More specifically, we want to use TeX package listings to include
source code,
[which btw in the mean time works
See ?system.file with the package= argument.
On Fri, Oct 10, 2008 at 2:19 PM, Peter Ruckdeschel
[EMAIL PROTECTED] wrote:
Hi,
this may be slightly off-topic, but as you are the experts:
we have written a small vignette, in which we want to refer to
.R, .Rd source files by means of relative
Gabor Grothendieck schrieb:
See ?system.file with the package= argument.
Thank you Gabor,
but this refers to the /installed/ package, while we are needing
path information about the not-yet-built source code of the
package during R CMD check / build.
Peter
Try placing a copy of the files in the inst directory and then
accessing them via system.files(myfile.R, package = mypackage)
or place them in the same directory as the Sweave file
and then access them without a directory path at all:
readLines(myfile.R)
On Fri, Oct 10, 2008 at 2:48 PM, Peter
Thanks again Gabor, for your quick reply,
Try placing a copy of the files in the inst directory and then
accessing them via system.files(myfile.R, package = mypackage)
you mean I should do this in an S-chunk in the .Rnw file?
I.e., running Sweave on it would then produce the copy into my
On Fri, Oct 10, 2008 at 7:06 PM, Peter Ruckdeschel
[EMAIL PROTECTED] wrote:
Thanks again Gabor, for your quick reply,
Try placing a copy of the files in the inst directory and then
accessing them via system.files(myfile.R, package = mypackage)
you mean I should do this in an S-chunk in the
