Re: [R-pkg-devel] handling documentation build tools

2024-05-21 Thread Vladimir Dergachev
Tuesday, May 21, 2024 2:15 PM To: Boylan, Ross Cc: r-package-devel@r-project.org Subject: Re: [R-pkg-devel] handling documentation build tools !---| This Message Is From an External Sender This message came from outside yo

Re: [R-pkg-devel] handling documentation build tools

2024-05-21 Thread Simon Urbanek
Ross, It's entirely up to you how you do this -- what you describe is something that has to happen before your run R CMD build, so it's not reflected in your package that you submit (and this has nothing to do with CRAN or R). There is nothing automatic as it requires you to do something in any

Re: [R-pkg-devel] handling documentation build tools

2024-05-21 Thread Boylan, Ross via R-package-devel
Ross Cc: r-package-devel@r-project.org Subject: Re: [R-pkg-devel] handling documentation build tools !---| This Message Is From an External Sender This message came fro

Re: [R-pkg-devel] handling documentation build tools

2024-05-21 Thread Dirk Eddelbuettel
As lyx is not listed in 'Writing R Extensions', the one (authorative) manual describing how to build packages for R, I would not assume it to be present on every CRAN machine building packages. Also note that several user recently had to ask here how to deal with less common fonts for style files

[R-pkg-devel] handling documentation build tools

2024-05-21 Thread Boylan, Ross via R-package-devel
I have some documentation that requires external tools to build. I would like to build the automatically, with requiring either users or repositories to have the tools. What's the best way to accomplish that. Specifically one document is written using the LyX word processor, so the "source" i