[R-pkg-devel] Submitting a package to C-RAN

I am trying to submit a package to CRAN. It did not pass the automated checks. However, I don't understand what it is I am supposed to fix. I have run R CMD check ... -- as-cran and it seems to pass. And I have also verified that it installs and works on ubuntu and windows. The message I get

Re: [R-pkg-devel] Submitting a package to C-RAN

Thanks for your help! I misunderstood the purpose of 'notes' and was only looking for errors/warnings. Also, could you update RccpMsgPack to use the latest version? On Sun, Sep 3, 2017 at 7:48 AM, Dirk Eddelbuettel wrote: > > Per

Re: [R-pkg-devel] Submitting a package to C-RAN

Sure thing. How did you want to merge them? On Sun, Sep 3, 2017 at 12:27 PM, Dirk Eddelbuettel <e...@debian.org> wrote: > > On 3 September 2017 at 11:36, Travers Ching wrote: > | Thanks for your help! I misunderstood the purpose of 'notes' and was > only > | lookin

Re: [R-pkg-devel] Configure dot win file preventing compilation for i386 on windows

Thanks Gabor and Duncan, that seems to be the issue. On Wed, Feb 13, 2019 at 9:53 AM Duncan Murdoch wrote: > > On 13/02/2019 12:45 p.m., Travers Ching wrote: > > I have a package in which I thought would be helpful to have a > > configure.win file. However, when compilin

[R-pkg-devel] Configure dot win file preventing compilation for i386 on windows

I have a package in which I thought would be helpful to have a configure.win file. However, when compiling (locally as well as through win-builder) I get the following message: "Warning: this package has a non-empty 'configure.win' file, so building only the main architecture" And then win

Re: [R-pkg-devel] set PKG_CONFIG_PATH before installing a package

I think the correct way to do it is through the configure script. See for example the Cairo package that uses pkg-config. Configure scripts are slightly hard to work through in my experience, but are worth it if you need customization of the installation environment. Travers On Mon, Apr 8,

Re: [R-pkg-devel] set PKG_CONFIG_PATH before installing a package

> On 8 April 2019 at 10:59, Travers Ching wrote: > | I think the correct way to do it is through the configure script. See > | for example the Cairo package that uses pkg-config. Configure scripts > | are slightly hard to work through in my experience, but are worth it > | if yo

Re: [R-pkg-devel] Executable file warning in CRAN check

ithub.com/cran/qs/blob/0.14.1/src/LZ4/LICENSE, which says > > > Executable File | 25 lines (20 sloc) | 1.28 KB > > On a Unix-based system you could do > > > chmod -x src/LZ4/LICENSE > > to remove the executable bit from that file. > > Cheers, > > S

[R-pkg-devel] How do I tell which alt-rep methods need to be implemented?

Greetings, I have a package with alt-rep strings and I just learned from a bug report that the "set_elt" method is required based on an interaction with another package. Error: "ALTSTRING classes must provide a Set_elt". Previously, I thought this function wasn't necessary to implement, based

Re: [R-pkg-devel] Warning about "serialize/load".

> Why are you against the futures and all the new shiny things? ;-) Sometimes one does not have control over these things, still using R 3.2 on some systems! ;o On Sun, Jul 14, 2019 at 5:43 PM Dirk Eddelbuettel wrote: > > On 14 July 2019 at 17:06, Travers Ching wrote: > |

Re: [R-pkg-devel] Warning about "serialize/load".

I think the major change was saving of alt-rep objects efficiently. Example save(1:1e8, file=...) is very efficient. I'm not sure if that is all that changed it, but I couldn't find documentation on the differences. For maximum compatibility in a package, personally I would use version 2. On

Re: [R-pkg-devel] Problems installing dependences of my package

Hi Andrea, If your code is highly dependent on a specific version, another option is to include their code directly in your package. The forecast package is under GPL-3 license, meaning you can use their code. You would just need include the authors as a contributor ([ctb] tag) and make note of

Re: [R-pkg-devel] Optional library dependencies for compiled code

I'd like to add, for bundling `zstd` and `lz4`, I was told by Professor Ripley that I must first check for system installations and use that when possible, because of possible security issues being fixed in later updates. I think that's a good idea, and can be set up with a configure script: 1)

[R-pkg-devel] CRAN no longer checking for solaris?

I see that there doesn't exist a Solaris flavor on any CRAN check page. However, I'm certain that Solaris was being checked up until very recently. Is this just temporary? Is there any information for the future of Solaris on CRAN? [[alternative HTML version deleted]]