Not sure if it's already been said, but note that we can only use
'Additional_repositories' for *optional* dependencies, which are
listed under 'Suggests' (and less used 'Enhances'). We cannot use
them for *hard* dependencies, which are listed under 'Depends' or
'Imports'. From the CRAN Policies
(
On 16 November 2022 at 06:36, Duncan Murdoch wrote:
| On 15/11/2022 11:59 p.m., Hugh Parsonage wrote:
| > I think you've misunderstood that excerpt. By "temporary development
| > state", it means _between_ CRAN releases; packages in a development
| > state are not suitable for CRAN, as the polic
Hello.
As already pointed out, the current R implementation treats any
non-empty value on _R_CHECK_LIMIT_CORES_ different from "false" as a
true value, e.g. "TRUE", "true", "T", "1", but also "donald duck".
Using '--as-cran' sets _R_CHECK_LIMIT_CORES_="TRUE", if unset. If
already set, it'll not t
On 14 November 2022 at 16:34, Elysée Aristide wrote:
| I was convinced that the issue is local. The warning message only appears
| on MAC.
| I did not try with another computer. I used CRAN macbuilder service and got
| the warning message. I guess this is also the computer CRAN uses.
Some furthe
Hi Ivan,
thanks for the info, I changed the check as you pointed out and it
worked. R CMD build and R CMD check --as-cran run without errors or
warnings on Linux + MacOS. However, I uploaded the package again at the
WINBUILDER service and obtained the following weird error:
* checking re-build
On 15/11/2022 11:59 p.m., Hugh Parsonage wrote:
I think you've misunderstood that excerpt. By "temporary development
state", it means _between_ CRAN releases; packages in a development
state are not suitable for CRAN, as the policy states:
CRAN hosts packages of publication quality and is not
