Henrik,
I completely agree with everything you wrote, but note that the issue at hand
is using `:::' in *the same* package, for example when a package needs to
access its own internal functions from an outside context, where running on a
cluster node set up by the package is one thing I can th
ware of it
before.
Best,
Cesko
Op 14-08-2020 om 22:31 schreef Joshua Ulrich:
On Fri, Aug 14, 2020 at 2:54 PM Duncan Murdoch wrote:
On 14/08/2020 3:08 p.m., Cesko Voeten wrote:
A while ago, I submitted an update to my package 'buildmer' that does not pass
R CMD check. This is del
A while ago, I submitted an update to my package 'buildmer' that does not pass
R CMD check. This is deliberate. The package contains functionality to run on
cluster nodes that were set up by the user and needs to access its own internal
functions from there. In previous versions of the package,
Package B should import only the packages and functions that are used by
package B. If package B does not use functions from package C, package B should
not import package C. What package A does is package A's problem, not package
B's. If package A requires package C, install.packages() will au
