On 14.09.2023 23:35, Leonard Mada wrote:
Dear Uwe,
I found out what is going on. There is an example:
## Write the pdb object in file "Rpdb.pdb" into the current directory
write.pdb(pdb, file = "Rpdb.pdb")
In examples, you should write to tempdir(), if at all.
Best,
Uwe Ligges
The
Dear Uwe,
I found out what is going on. There is an example:
## Write the pdb object in file "Rpdb.pdb" into the current directory
write.pdb(pdb, file = "Rpdb.pdb")
The example was present in the previous version as well. So I did not
thought about it. I do not know how to handle this: altho
The spellng is fine and not a problem.
For
* checking for non-standard things in the check directory ... NOTE
Found the following files/directories:
‘Rpdb.pdb’
You need to move this to ./inst or a subdirectory or, if data, consider
./extdata See Writing R Extensions.
Best,
Uwe Ligges
On 14
Regarding PDB, in Rd format it’s best to wrap that in an \acronym{} tag. See
section 2.3 of https://cran.r-project.org/doc/manuals/R-exts.html#Marking-text
Avi
Sent from my iPhone
> On Sep 14, 2023, at 3:40 PM, Leonard Mada via R-package-devel
> wrote:
>
> Dear List Members,
>
> After resu
Dear List Members,
After resubmitting the updated version of the Rpdb package (2.3.1), the
following Notes were generated:
1.) Spelling PDB
https://win-builder.r-project.org/incoming_pretest/Rpdb_2.3.1_20230914_173458/Windows/00check.log
https://win-builder.r-project.org/incoming_pretest/Rpdb_
Dirk,
Providing a partial answer: Simon replied earlier today to my related
question; macOS builds had been blocked, but are starting to flow again.
> one package managed to spawn a separate process that was blocking the
build process (long story) and I was on the other side of the world. It
shou
Simon,
A new package of mine [1] appeared on CRAN on Sep 5. Respecting the one week
gap,
I made a small update on Sep 12.
Today is Sep 14. There are still no builds for
macOS r-release (arm64)
macOS r-oldrel (arm64)
macOS r-release (x86_64)
but we do have two oldrel releases. Weirder sti
