I do not know devtools, but the vignette sources should be placed in
./vignettes and then R CMD build will put the files into the relevant
places automatically.
Best,
Uwe Ligges
On 07.04.2017 07:55, David Hugh-Jones wrote:
Okay, so this got tumbleweeded... so should I file a bug?
D
On
Okay, so this got tumbleweeded... so should I file a bug?
D
On Thu, 6 Apr 2017 at 15:37, David Hugh-Jones
wrote:
>
> Before building my package, I manually place both pdf and html versions of
> my vignettes into inst/doc. I then build the package with `devtools::check`.
>
> Listing of the resu
With `BuildVignettes: no` in my DESCRIPTION and `^vignettes` in my
.Rbuildignore, I can squeak through a normal build (no `r_build_args` or
`r_check_args`) on travis with just this note:
* checking for old-style vignette sources ... NOTE
Vignette sources only in ‘inst/doc’:
‘rslurm
On 6 April 2017 at 20:17, Ian Carroll wrote:
| How do I package an rmarkdown vignette that cannot be built on win-builder?
The vignette in question demonstrates interaction with a SLURM cluster, which
is not available to win-builder or travis. In my `.travis.yml` I can include
`r_build_args: "-
On 2 April 2017 at 17:21, Alexandre Sieira wrote:
| Hi, everyone.
|
| I have done some work this weekend to allow the SnakeCharmR package (
| https://github.com/asieira/SnakeCharmR) to be compiled under Windows. For
| reference, this is an Rcpp-based packages that links to the system's
| libpytho
Hello,
First post to r-package-devel, thanks for your help.
How do I package an rmarkdown vignette that cannot be built on win-builder? The
vignette in question demonstrates interaction with a SLURM cluster, which is
not available to win-builder or travis. In my `.travis.yml` I can include
`r_
Before building my package, I manually place both pdf and html versions of
my vignettes into inst/doc. I then build the package with `devtools::check`.
Listing of the resulting tarball:
-rw-r--r-- 0 david staff1692 6 Apr 15:10
huxtable/inst/doc/design-principles.R
-rw-r--r-- 0 david sta
