[R-pkg-devel] R CMD Check warning about vigentte dates

[Paul Buerkner]

Dear list,

I recently submitted a new version of my package (brms) to CRAN. It was
accepted by the CRAN team, but multiple operating systems (mainly unix) now
complain about

"Files in the 'vignettes' directory newer than all files in 'inst/doc':"

I have checked and all the files in "inst/doc" have a newer date than in
"vignettes". Also,
the error does not occur when running R CMD Check --as-cran locally or on
winbuilder.

I am very grateful for any ideas how to fix that.

- Paul

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Validate CRAN package using a linked library

[Dorel, Mathurin]

Thanks for your replies,

I was not aware that LinkingTo was only a static linking. So no BH-like 
solution.
But how does the DLL pulling work then (I won't use it, it does not sound like 
a good practice but I'm curious)

I'll looked at nloptr, it looks like an elegant solution, I'll try that.

Mathurin


De : Dirk Eddelbuettel [e...@debian.org]
Envoyé : mercredi 14 septembre 2016 23:54
À : Martyn Plummer
Cc : Dirk Eddelbuettel; Dorel, Mathurin; r-package-devel@r-project.org
Objet : Re: [R-pkg-devel] Validate CRAN package using a linked library

On 14 September 2016 at 20:38, Martyn Plummer wrote:
| Most people who want to interface to an external library embed the source 
code of the library in their R package. I see that ginac is a C++ library which 
creates additional problems. Only a few R packages  interface to an external 
C++ library (e.g. the interfaces to SYMPHONY, gdal,  QuantLib, and JAGS).

No, there are lots more these days; look eg at many of the packages Jeroen
has added in the last year or two.

I also have several few more, and/or helped a few.  nloptr is an example I
like because Jelmer and I generalized it to _either_ use embedded source
(slower build) or use the system library where present (ie Debian/Ubuntu).

| Windows is a problem because the toolchain used by R uses static linking to 
the C++ runtime. This has two  side effects:
|
| 1)  Both the R package and the external DLL must be built with the same 
toolchain. So you can't just ask CRAN to install the Windows binary from the 
ginac web site.
|
| 2) You can't throw an exception across DLL boundaries.
|
| As Dirk says, this is hard.

Yes.  And getting libraries to Windows in a sane way is still an open
problem.  Some of us cheat by pulling prebuilt DLLs from, say, GitHub during
build time.  Works, but is more or less an open barn door waiting for trouble.

So in general: "it depends". But no shortcuts.

Dirk

--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] R CMD Check warning about vigentte dates

[Duncan Murdoch]

On 15/09/2016 6:29 AM, Paul Buerkner wrote:

Dear list,

I recently submitted a new version of my package (brms) to CRAN. It was
accepted by the CRAN team, but multiple operating systems (mainly unix) now
complain about

"Files in the 'vignettes' directory newer than all files in 'inst/doc':"

I have checked and all the files in "inst/doc" have a newer date than in
"vignettes". Also,
the error does not occur when running R CMD Check --as-cran locally or on
winbuilder.

I am very grateful for any ideas how to fix that.


This is a new test in R-devel, and it's still undergoing some 
refinement.  It has issued some false warnings when there are problems 
reading the modification time of a file -- not all files have valid times.


I think those are now fixed (as of revision 71254); if you're seeing 
problems using a newer version, I'd appreciate seeing a copy of the 
tarball that causes them.


Duncan Murdoch

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel