On Thu, Mar 15, 2018 at 12:27 PM, Rainer Krug
wrote:
>
> Yes - that is definitely true, but the one does not exclude the other. I
> actually think giving permission once, and than forgetting about it, is
> worse than knowing: Stop - user configuration is loaded - unless I tell it
> not to be load
Hi Gabor,
That's indeed the case, but I see good reasons for the CRAN policy when we
take reproducability into account. Afaik, CRAN and R always strived to
provide tools that give the same output regardless of the machine they're
running on when opened in a fresh R session. If packages store setti
This seems to be a good occasion to note that the CRAN policy does not
seem to conform
the industry standards. Applications can actually store user level
configuration information,
cached data, logs, etc. in the user's home directory, and there
standard way to do this.
Here is the Apple recommenda
Duncan gave one option. The other option is to provide a specific
write2disk() function or so that allows the user to determine whether
he/she wants to save the data. Then the user can decide exactly where he
wants to find it.
The other important part is the format in which it's saved. Users can
s
On 12/03/2018 6:26 PM, Roy Mendelssohn - NOAA Federal wrote:
Hi All:
Recently there was a proper admonishment to a developer that it is bad etiquette writing
to a user's home directory, and for temporary files use the functions tempdir() and
tempfile(). I am working on a new package (present
