Dear Hadley,
many thanks for your comment and much more for your fantastic tutorial
and packages! I essentially learned (and still learn) package
development by your tutorial. In the concrete case, changing some
settings finally did it and devtools worked like charm. I want to thank
you for
Yes, I certainly will do that. I've checked on win-builder and the package
seems to pass, so my examples seem to be in good order.
David
On Sat, 8 Dec 2018 at 15:17, Dirk Eddelbuettel wrote:
>
> On 8 December 2018 at 14:41, David Hugh-Jones wrote:
> | Thanks guys. If CRAN already sets
On 8 December 2018 at 14:41, David Hugh-Jones wrote:
| Thanks guys. If CRAN already sets FORCE_SUGGESTS = false, then I think I
| don't have a problem.
I think you still do as long as you ignore Duncan's advice. It's not "just"
about skirting CRAN tests and rules, it is about doing packaging
Thanks guys. If CRAN already sets FORCE_SUGGESTS = false, then I think I
don't have a problem.
David
On Sat, 8 Dec 2018 at 14:36, Duncan Murdoch
wrote:
> On 08/12/2018 9:28 AM, Hadley Wickham wrote:
> > Can you just set _R_CHECK_FORCE_SUGGESTS_=false?
> >
> > env:
> >global:
> ># don't
You might try reinstalling devtools and dependencies - there was
unfortunately a brief combination of versions that lead to build()
failing to overwrite existing files.
Hadley
On Fri, Dec 7, 2018 at 10:46 AM Wolfgang Lenhard
wrote:
>
> Many thanks for the remark. It seems, it has something to do
Can you just set _R_CHECK_FORCE_SUGGESTS_=false?
env:
global:
# don't treat missing suggested packages as error
- _R_CHECK_FORCE_SUGGESTS_=false
I am reasonably certain that is what CRAN uses.
Hadley
On Fri, Dec 7, 2018 at 9:11 AM David Hugh-Jones
wrote:
>
> Hi,
>
> My package Suggests
