On Wed, 17 Apr 2019 at 02:41, Roy Mendelssohn - NOAA Federal via
R-package-devel wrote:
> -- Forwarded message --
> From: Roy Mendelssohn - NOAA Federal
> To: "Maëlle SALMON via R-package-devel"
> Cc:
> Bcc:
> Date: Tue, 16 Apr 2019 17:41:21 -0700
> Subject: Vignette timing out o
On Tue, 16 Apr 2019 at 20:54, Tan Zhou wrote:
>
> Hi Iñaki and Ralf,
> Thank you very much for your help and suggestions.
> Yes, I followed instruction and did that. Now I have the
> https://tankwin08.github.io/drat.
> But I test
>
> install.packages("rPeaks")
> Installing package into ‘C:/Users/
On Tue, 16 Apr 2019 at 19:57, Will wrote:
>
> Hello everyone,
>
> I'm sorry to bother you, but I would like some help getting a package (
> *suppdata*; https://github.com/ropensci/suppdata) available through CRAN.
> The package downloads supplementary materials from papers and data
> repositories
You could convince the original author to submit rPeaks to CRAN, or
volunteer to be the maintainer and do it yourself if he doesn't want
to maintain it. That would be easier for you and better for everyone,
because the package would be well-checked under the watchful eye of
CRAN maintainers. Otherw
On Sat, 9 Mar 2019 at 15:07, Roger Bivand wrote:
>
> Hi,
>
> Is anyone aware of tools permitting the listing of functions in the
> namespace of package A used by package B when package B declares that it
> depends on A, suggests A, or imports(A) without specifying the functions
> from A that B is
On Tue, 26 Feb 2019 at 18:38, Oliver Dechant wrote:
>
> Somewhat relatedly is there a way to monitor when a package has new
> reverse depends or imports added?
I don't know of any service currently providing this, if that's what
you're asking. But it's pretty straightforward to set up a cron job
On Tue, 26 Feb 2019 at 05:29, Peter Carbonetto
wrote:
>
> I'm wondering if there is a way to get a list of reverse dependencies on
> CRAN that includes archived packages.
>
> I am asking because "ashr", an R package I maintain, was recently removed
> from CRAN, and now it is back after I fixed the
See an example with roxygen2:
https://github.com/r-quantities/errors/blob/master/R/data.R
And how this is translated if you prefer to write the Rd yourself:
https://github.com/r-quantities/errors/blob/master/man/datasets.Rd
Iñaki
On Mon, 14 Jan 2019 at 15:45, Troels Ring wrote:
>
> Dear frien
On Fri, 11 Jan 2019 at 17:31, Troels Ring wrote:
>
> Dear friends - I'm slowly learning to make packages in RStudio and it seems
> impressive. I managed now to have my acidbase package pass the check-package
> test with this result
>
>
>
> > checking R code for possible problems ... NOTE
>
> pH_
On Thu, 10 Jan 2019 at 23:27, Dirk Eddelbuettel wrote:
>
>
> On 10 January 2019 at 22:33, Iñaki Ucar wrote:
> | On Thu, 10 Jan 2019 at 21:55, Dirk Eddelbuettel wrote:
> | > Comes up with an empty / unset olddir when I do
> | >
> | > R CMD build someNameHere; R
On Thu, 10 Jan 2019 at 21:55, Dirk Eddelbuettel wrote:
>
>
> On 9 January 2019 at 17:57, Iñaki Ucar wrote:
> | Did you check Sys.getenv("OLDPWD")? I checked with a knitr vignette
> | and the correct path was there.
>
> Code:
>
> [...]
>
> <>=
It just ocurred to me the following. Instead of
R CMD build pkg
I've tried this:
cd pkg; R CMD build --log `pwd`
and voilà: the tarball includes a log file, and inside there's the
complete path to the DESCRIPTION.
Iñaki
On Wed, 9 Jan 2019 at 20:33, Duncan Murdoch wrote:
>
> On 09/01/2019 11:
On Wed, 9 Jan 2019 at 17:39, Dirk Eddelbuettel wrote:
>
>
> Hi Duncan and Iñaki,
>
> On 4 January 2019 at 14:13, Duncan Murdoch wrote:
> | If you want a total hack, the help system can run R code during a build,
> | e.g. \Sexpr[stage=build]{paste("Built at", Sys.time())}. Certainly it
> | could e
On Tue, 8 Jan 2019 at 08:39, Sebastian Meyer wrote:
>
> To fix method lookup for R >= 3.6.0, you can use delayed S3 method
> registration along the lines of:
>
> if (getRversion() >= "3.6.0") {
> S3method(pkg::gen, cls)
> }
And to add this automatically to your NAMESPACE with roxygen2, you may
On Fri, 4 Jan 2019 at 20:10, Iñaki Ucar wrote:
>
> I see. Then I suggest the following hack (not tested). If the package
> has a vignette, put there a hidden chunk that generates a file with
> info about the branch and the path. This file will be available for
> your configure scr
On Fri, 4 Jan 2019 at 19:42, Dirk Eddelbuettel wrote:
>
>
> On 4 January 2019 at 19:24, Iñaki Ucar wrote:
> | On Fri, 4 Jan 2019 at 16:43, Dirk Eddelbuettel wrote:
> | >
> | >
> | > For a few years now I had mused about how nice it would be to have other
> |
On Fri, 4 Jan 2019 at 16:43, Dirk Eddelbuettel wrote:
>
>
> For a few years now I had mused about how nice it would be to have other
> scripts triggered like `cleanup`. For Rcpp, it would be nice to run
> compileAttributes(). For roxygen2, it would be nice to run roxygenize()
> (especially if tha
El lun., 1 oct. 2018 a las 14:45, Müller, Bernd
() escribió:
>
> Dear Sir or Madam,
>
> On Friday, I submitted my packae epos_0.1.0 via the web submission system
> https://cran.r-project.org/submit.html without any further errors, warnings,
> and notes except this one:
>
> * checking CRAN incomin
El vie., 7 sept. 2018 a las 16:03, Ralf Stubner
() escribió:
>
> On 07.09.2018 15:52, Iñaki Ucar wrote:
> > For the record, this is what the testthat paper in the R Journal says:
> >
> > "[...] I recommend storing your tests in inst/tests/ (so users also
> > h
El vie., 7 sept. 2018 a las 15:28, Dirk Eddelbuettel
() escribió:
>
>
> On 7 September 2018 at 13:08, Gábor Csárdi wrote:
> | On Fri, Sep 7, 2018 at 12:29 PM Dirk Eddelbuettel wrote:
> | >
> | >
> | > On 7 September 2018 at 09:27, Gábor Csárdi wrote:
> | > | When are users running tests for packag
ger(model1$nf),
> as.integer(model1$fsize), as.integer(model1$bnum), as.double(model1$min),
> as.double(model1$max), as.integer(model1$flist), as.integer(model1$w),
> as.double(model1$pc), ye=integer(nr), prob=double(nr*model1$c) )
>
> }
> With rega
101 - 121 of 121 matches
Mail list logo
