Hi Team,
I mentioned some comment before uploading the package for publishing i.e. "My
package RIBMDB has a dependency on CLI driver which has some IBM proprietary C
code due to which it cannot be included as part of package and needs
executables i.e. dll or .so file depending on the platform i.
Pls write your message to c...@r-project.org
Best,
Uwe Ligges
On 30.03.2021 09:05, Binit Kumar wrote:
Hi Team,
I mentioned some comment before uploading the package for publishing i.e. "My
package RIBMDB has a dependency on CLI driver which has some IBM proprietary C code due
to which it cann
Hi Team,
I am trying to add an optional system/C++ library to my package and was
wondering if anyone could point me in the right direction on how to do this
in the R package ecosystem.
To be concrete, I want my graphics device package httpgd to be able to call
into imagemagick/magick++ to add ima
On 30 March 2021 at 15:19, Florian Rupprecht wrote:
| I am trying to add an optional system/C++ library to my package and was
| wondering if anyone could point me in the right direction on how to do this
| in the R package ecosystem.
|
| To be concrete, I want my graphics device package httpgd t
On 30 March 2021 at 01:10, Rasmus Liland wrote:
| Dirk, I did not realize libiodbc[1] is an
| alternative to unixODBC, how are you
| able to see this?
By studing the sources and README of the package you are trying to build.
| I also did not realize I had both of
| them installed ...
|
Hi,
When running R CMD check on R-devel, a CRAN note appears about
\href{https://doi.org/...}{label} in Rd files. Like:
Found the following URLs which should use \doi (with the DOI name only):
File ‘read_GRTSmh.Rd’:
https://doi.org/10.5281/zenodo.2611233
https://doi.org/10.5281/zenod
On 30/03/2021 9:44 a.m., Floris Vanderhaeghe wrote:
Hi,
When running R CMD check on R-devel, a CRAN note appears about
\href{https://doi.org/...}{label} in Rd files. Like:
Found the following URLs which should use \doi (with the DOI name only):
File ‘read_GRTSmh.Rd’:
https://doi.org/1
> I just tried \doi{10.5281/zenodo.2611233} and it worked.
Sure, but what about making a hyperlink to
https://doi.org/10.5281/zenodo.2611233 while showing "text" in the
documentation, as in \href{wwwaddress}{text}. I assume the CRAN note
appears because it wants literal DOI strings in the doc
> When running R CMD check on R-devel, a CRAN note appears about
> \href{https://doi.org/...}{label} in Rd files...
>... Can this be resolved using \doi{} as suggested, while still resulting in a
>working link to doi.org? I didn't find a way to do that.
This is a recent addition to R checks. I a
On 30/03/2021 10:39 a.m., Floris Vanderhaeghe wrote:
I just tried \doi{10.5281/zenodo.2611233} and it worked.
Sure, but what about making a hyperlink to
https://doi.org/10.5281/zenodo.2611233 while showing "text" in the
documentation, as in \href{wwwaddress}{text}. I assume the CRAN note
appear
On 30/03/2021 12:36 p.m., Duncan Murdoch wrote:
On 30/03/2021 10:39 a.m., Floris Vanderhaeghe wrote:
I just tried \doi{10.5281/zenodo.2611233} and it worked.
Sure, but what about making a hyperlink to
https://doi.org/10.5281/zenodo.2611233 while showing "text" in the
documentation, as in \href
Op 30/03/2021 om 18:46 schreef Duncan Murdoch:
On 30/03/2021 12:36 p.m., Duncan Murdoch wrote:
On 30/03/2021 10:39 a.m., Floris Vanderhaeghe wrote:
I just tried \doi{10.5281/zenodo.2611233} and it worked.
Sure, but what about making a hyperlink to
https://doi.org/10.5281/zenodo.2611233 while
12 matches
Mail list logo
