Good day,
I often notice that some lines of code in many PDF manuals generated for CRAN
packages run off the page. Perhaps the maximum number of characters per line
should be stated in section 2.16 of Writing R Extensions. It would help package
authors like me write better Rd files.
--
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
Hi, I'm stuck. I am using a function called col_concat from the package
{assertr}. But when I list it as a dependency, either by
import(assertr)
or
importFrom("assertr", "col_concat")
---
I get this error message:
* checking package dependencies ... ERROR
Namespace dependency not r
On 21 November 2017 at 16:51, Duncan Murdoch wrote:
| According to section 1.2.1 "Using Makevars" in Writing R Extensions,
| R_HOME/etcR_ARCH/Makeconf is included after Makevars, so what you're
| seeing is by design. I believe this is so that packages are built with
| tools compatible with tho
On 21/11/2017 3:37 PM, Dirk Eddelbuettel wrote:
Having a bit of a puzzle with a package at work (which I can't share).
In src/Makevars I override CC, CXX, CXX11, CXX14 to point to a specific
(version) of g++ on my system, say g++-x.y. I also set CXX_STD=CXX14
Only it doesn't work. I need an e
Having a bit of a puzzle with a package at work (which I can't share).
In src/Makevars I override CC, CXX, CXX11, CXX14 to point to a specific
(version) of g++ on my system, say g++-x.y. I also set CXX_STD=CXX14
Only it doesn't work. I need an extra dot.RMakevars and an invocation via
R_MAKE
I think you're right, and I think I've found the offending code
(https://github.com/patperry/r-utf8/blob/master/src/as_utf8.c#L111):
if (!raw || ce == CE_BYTES || ce == CE_NATIVE) {
if (!duped) {
PROTECT(ans = duplicate(ans)); nprot++;
duped = 1;
}
On 21.11.2017 10:15, Martin Maechler wrote:
Paul Johnson
on Mon, 20 Nov 2017 14:59:26 -0600 writes:
> I mistakenly left a write in "/tmp" in the rockchalk package (version
> 1.8.109) that I uploaded last Friday. Kurt H wrote and asked me to fix
> today.
> While uplo
Hi,
Just in case it makes some sense, the same Matrix-related error occurs
at least for these other packages:
matchMulti 1.1.6
compound.Cox 3.6
mpmcorrelogram 0.1-4
epr 3.0
icensBKL 1.1
Marcelino
El 21/11/2017 a las 10:15, Martin Maechler escribió:
Paul Johnson
On Mon, Nov 20, 2017 at 8:34 PM, Patrick Perry wrote:
> One of my packages has what I believe to be spurious rchk warnings:
>
> From
> https://raw.githubusercontent.com/kalibera/cran-checks/master/rchk/results/utf8.out
>
> Package utf8 version 1.1.0
> Package built using 73757/R 3.5.0; x86_64-pc-l
> Paul Johnson
> on Mon, 20 Nov 2017 14:59:26 -0600 writes:
> I mistakenly left a write in "/tmp" in the rockchalk package (version
> 1.8.109) that I uploaded last Friday. Kurt H wrote and asked me to fix
> today.
> While uploading a new one, I became aware of a probl
14 matches
Mail list logo
