One way to avoid burying the conditional deep into the code is to put it in
.onLoad(). When the author of a dependency informed me that from v.2.0.0
"as.polylist would be renamed I put the following in .onLoad():
.onLoad <- function(libname, pkgname){
if (utils::packageVersion("PolynomF") >
On Mon, 22 Feb 2021 at 11:46, Georgi Boshnakov
wrote:
>
> One way to avoid burying the conditional deep into the code is to put it in
> .onLoad(). When the author of a dependency informed me that from v.2.0.0
> "as.polylist would be renamed I put the following in .onLoad():
>
> .onLoad <- funct
On Sun, Feb 21, 2021 at 3:47 PM Iñaki Ucar wrote:
>
> Hi,
>
> Let's say that pkgA uses pkgB::function1. Then, version 2 of pkgB
> removes function1 and exports function2 for the same functionality. So
> pkgA does something along these lines:
>
> if (utils::packageVersion("pkgB") < 2) {
> pkgB::f
> This works for a renamed function. But if the function also changes
> arguments, it doesn't work anymore.
Indeed, didn't think about that. I forgot to mention also that the NOTE appears
only with the old version of the dependency, so it disappears after a couple of
years.
FWIW, CRAN accepts
Am 22.02.21 um 11:06 schrieb Knut Krueger:
> I was suggested: "A citation in the Description file is typically a good
> idea because people can think whether your package is appropriate
> before reading all docs and installing the package, just from reading
> the CRAN overview page."
>
> but I do
On Mon, 22 Feb 2021 at 11:55, Gábor Csárdi wrote:
>
> On Sun, Feb 21, 2021 at 3:47 PM Iñaki Ucar wrote:
> >
> > Hi,
> >
> > Let's say that pkgA uses pkgB::function1. Then, version 2 of pkgB
> > removes function1 and exports function2 for the same functionality. So
> > pkgA does something along th
On 22.02.2021 14:46, Knut Krueger wrote:
Am 22.02.21 um 12:07 schrieb Sebastian Meyer:
Example: Einstein et al. (1935) .
What is the syntax if I have multiple references f.e
For function foo1:
Autor1 (2000) >doi:23837454235r2354.45764>
Autor2 (2003) >doi:d73234k458f83.38358235>
For f
I was suggested: "A citation in the Description file is typically a good
idea because people can think whether your package is appropriate
before reading all docs and installing the package, just from reading
the CRAN overview page."
but I do not find hints how to implement the doi and the re
On 21 February 2021 at 19:52, Karim Rahim wrote:
| I'm in the process of incorporating some improvements that I pulled from
| github.
| I am getting a warning and a note. These occur when I run
|
| R CMD check --as-cran fftwtools_0.9-10.tar.gz
|
| 1.
| * checking whether package ‘fftwtools’ can
Am 22.02.21 um 12:07 schrieb Sebastian Meyer:
Example: Einstein et al. (1935) .
What is the syntax if I have multiple references f.e
For function foo1:
Autor1 (2000) >doi:23837454235r2354.45764>
Autor2 (2003) >doi:d73234k458f83.38358235>
For function foo2:
Autor3 (2013)
Regards Knut
I clicked yes that I have fixed all errors, because I have no idea to
fix Mac errors:
No protocol specified
No protocol specified
Warning in fun(libname, pkgname) : couldn't connect to display ":0"
Error in structure(.External(.C_dotTclObjv, objv), class = "tclObj") :
[tcl]
Hi Team,
I uploaded a package to CRAN but didn’t get any response on success or failure.
How to know the status of the same?
Thanks & Regards,
Binit Kumar
From: CRAN submission
Sent: 22 February 2021 20:53
To: CRAN
Subject: CRAN submission RIBMDB 1.0-21
EXTERNAL EMAIL
[This was generated f
On Tue, 23 Feb 2021 02:03:34 +
Binit Kumar wrote:
> I uploaded a package to CRAN but didn’t get any response on success
> or failure. How to know the status of the same?
Glad to know you were able to solve the check problems!
Your package is currently waiting in the queue to be automaticall
13 matches
Mail list logo
