Thank you again for your responses Rodrigo Tobar. I'm happy to call this a
solution. I've got some testing to do but I'm hoping to get this sent back
to CRAN soon.
Thank you for your help!
Brian
On Tue, Aug 11, 2020 at 11:28 PM Rodrigo Tobar wrote:
> Hi Brian,
>
> On 12/8/20 10:21 am, brian kna
Hi Brian,
On 12/8/20 10:21 am, brian knaus wrote:
[...] It sounds like I can assume that CRAN machines will have
```checkbashisms``` installed where necessary
That's my reading, yes.
and handle this appropriately when not?
I don't think you need to handle this at all. As you experimented,
Thank you Dirk "Eddelbuettel" (apologies for my spelling, it's your name,
so I should be able to spell it correctly, particularly if I'm asking you
for help) and Rodrigo Tobar for the responses! It sounds like I've gone
down a rabbit hole that I should not have.
When I omit ```configure``` (in my
Hi Brian,
The checkbashisms script is invoked by the R checks automatically:
https://github.com/wch/r-source/blob/trunk/src/library/tools/R/check.R#L1216-L1267
Thus there shouldn't be any need for you to invoke it manually in your
configure script, even less so to worry about its presence. You
Hi R-pkg-devel,
My package
https://github.com/knausb/vcfR
has been archived on CRAN because I was asked by CRAN to address issues
that I was unable to address before the deadline I was given. The issue I'm
struggling with is that when I use
```
R CMD check --as-cran vcfR_1.12.0.tar.gz
```
I ge
