Dear Paul,
the correct form is something like:
if( requireNamespace("abind", quietly = TRUE) )
{ abind::foo() # do sth with abind} else {
message("you need to install the pkg abind for this example")
}
In general you should avoid sending out code that installs packages. Some
people work wit
Hi all,
I am relatively new in creating R packages. I have created a new package
called *"foo"* and submitted it to CRAN for review.
I am wondering the difference between "Imports" and "Suggests" dependencies
in DESCRIPTION file. According to my understanding, the "Imports" field
contains all pac
Cathy…
Regarding changes from last year, I wouldn’t worry too much about that. The
CRAN checking system is always moving toward greater stringency as the
ecosystem evolves. Requirements and messages change steadily.
I have “chased my tail” along the lines of your original description before a
On 21 November 2017 at 19:20, Cathy Lee Gierke wrote:
| Thanks Bryan. All of my imports are in the namespace. Can you tell me why
| this one should be in the description file?
Because you need an entry in the DESCRIPTION file _and_ an entry in NAMESPACE.
Dirk
--
http://dirk.eddelbuettel.com
Thanks Bryan. All of my imports are in the namespace. Can you tell me why
this one should be in the description file?
Cathy Lee Gierke
*“Darkness cannot drive out darkness: only light can do that. Hate cannot
drive out hate: only love can do that.” *
*“The arc of the moral universe is long, bu
Edit your DESCRIPTION file to include
imports: assertr
That’s why you get the "not required" message.
Bryan
> On Nov 21, 2017, at 7:54 PM, Cathy Lee Gierke wrote:
>
> Hi, I'm stuck. I am using a function called col_concat from the package
> {assertr}. But when I list it as a dependency, eit
