Re: [R-pkg-devel] DOI for archived package?

2020-09-10 Thread Jeff Newmiller
If your article is published with a DOI and read by anyone actually interested in it then it will be likely be accessed, so "never" seems rather pessimistic of you. You could simply not argue with your editor and acquiesce. On September 10, 2020 9:14:12 AM PDT, "Kevin R. Coombes" wrote:

Re: [R-pkg-devel] DOI for archived package?

2020-09-10 Thread Thierry Onkelinx
Dear Kevin, My git2rdata package is on CRAN, ROpenSci and Zenodo. The GitHub repo is linked to Zenodo, so every release on GitHub gets its own DOI. The benefit of the DOI is that it makes it easier for others to cite your package in a consistent manner. And you'll get a better overview of those

Re: [R-pkg-devel] Fixing travis build fail due to fftwtools fatal error (fftw3.h: No such file or directory)

2020-09-10 Thread Marta Karaś
Adding the following to .travis.yml: before_install: - if [ "$TRAVIS_OS_NAME" = "linux" ]; then sudo apt-get -y install libfftw3-dev ; fi did the trick! Thank you both for your attention to this issue! Bests, Marta Karas On Thu, Sep 10, 2020 at 8:35 AM Karim Rahim wrote: > Thanks, > >

Re: [R-pkg-devel] DOI for archived package?

2020-09-10 Thread Sean Davis
I have found reminding editors of this editorial to be useful: https://www.nature.com/articles/ng.2869 Community repositories that carry out testing are ideal for commonly used > programs (for example, those used in statistical analysis), and a fair > proportion of the genetics community is

Re: [R-pkg-devel] DOI for archived package?

2020-09-10 Thread Iñaki Ucar
If you proposed https://cran.r-project.org/src/contrib/Archive//_.tar.gz and the editor is suspicious about the "src/contrib/Archive" stuff, you could propose instead https://cran.r-project.org/package==, which *looks* more permanent I guess. Iñaki On Thu, 10 Sep 2020 at 18:14, Kevin R. Coombes

[R-pkg-devel] DOI for archived package?

2020-09-10 Thread Kevin R. Coombes
Hi, I am in the process of submitting a "workflow" article about an R package (which is onCRAN) to F1000Research. The associate editor that I am dealing with wants a "DOI" for the source code of the package being described in the manuscript.  I have already explained that CRAN archives all

Re: [R-pkg-devel] Fixing travis build fail due to fftwtools fatal error (fftw3.h: No such file or directory)

2020-09-10 Thread Karim Rahim
Thanks, That may be it. It is a missing dependency. It's been a while and I'm not sure which package exposes fftw3.h ... Karim On Thu, Sep 10, 2020 at 8:16 AM Dirk Eddelbuettel wrote: > > On 9 September 2020 at 23:45, Karim Rahim wrote: > | sudo apt-get install -y fftw3 > > Or maybe rather

Re: [R-pkg-devel] Fixing travis build fail due to fftwtools fatal error (fftw3.h: No such file or directory)

2020-09-10 Thread Dirk Eddelbuettel
On 9 September 2020 at 23:45, Karim Rahim wrote: | sudo apt-get install -y fftw3 Or maybe rather sudo apt-get install libfftw3-dev to get the development headers? Dirk | Then try again. | | Let me know if it doesn't work. | | Cheers! | Karim | | On Wed, Sep 9, 2020 at 10:27 PM Max

Re: [R-pkg-devel] Fixing travis build fail due to fftwtools fatal error (fftw3.h: No such file or directory)

2020-09-10 Thread Karim Rahim
sudo apt-get install -y fftw3 Then try again. Let me know if it doesn't work. Cheers! Karim On Wed, Sep 9, 2020 at 10:27 PM Max Turgeon wrote: > > Hi Marta, > > One change I can see from your Git history that seems to match the first > failed build on Travis is when you added "Imports: