Hi Dirk,

Dirk Eddelbuettel wrote on 2020-07-23 15:16:
Helmut,

For previous uploads you affirmed that you read the CRAN Repository Policy
which states

      [...]

Your package appears to violate that requirement.

As I wrote previously the statement continues with
"Limited exceptions may be allowed in interactive sessions if the package obtains confirmation from the user."

I'm not a native speaker of English but for me "should not write" != "must not write".

  I would fix the package.

I removed the automatic switch to "~/" if no path is given. As before I recommend in the man-pages to give the full path. However, I _still_ state that "~/" _can_ be used for convenience. The package is used in a regulated environment. The output file contains an entire audit-trail (name of the user and system, version and date of the OS, R, all packages, functions used, time of execution, blablah). If the package would write to tempdir() I would have to add a warning in bold font of every man-page like "Execute the command tempdir() to find out where your result files reside. Copy the files to a safe location before you quit the R-session. If you fail to do so, your results will be lost."

Off topic: I don't like it that on Windows tempdir is located at "C:/Users/{Username}/AppData/Local/Temp/Rtmp..." I strictly separate my OSes (on C), software (on D), data (on E), backups (on F). Writing to the system disk is not what I prefer. However, in my installation "~/" resolves to "E:/Users/{Username}/Documents/"...

--
Ing. Helmut Schütz
BEBAC – Consultancy Services for
Bioequivalence and Bioavailability Studies
Neubaugasse 36/11
1070 Vienna, Austria
T +43 1 2311746
M +43 699 10792458
E helmut.schu...@bebac.at
W https://bebac.at/
C https://bebac.at/Contact.htm
F https://forum.bebac.at/
GIS 24799386, VAT ATU61115625, DUNS 300370568, EORI ATEOS1000096209
GDPR https://bebac.at/Data-Protection.htm

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

Reply via email to