Maybe dropbox can make things worse, if your package library happens
to be in Dropbox. (I would think this is not a good idea.)
But it does happen without Dropbox, and if you install packages
frequently, e.g. if you develop a bunch of packages, then it is a
familiar error, it does happen all the t
I wonder if Dropbox “smartsync” is the culprit here. I’ve noticed this
feature can create confusion between programs when Dropbox provides (a link
to) the file when it is opened but only when it recognizes the file is
being opened.
On Tue, 5 Nov 2019 at 7:46 pm, Gábor Csárdi wrote:
> I am not su
I am not sure what the first issue was, but the second is an old R
issue. It happens when you update a package while its package (or
help) database, the rdb file mentioned in the error message, is open
in the current R session, i.e. when the package is loaded. The
database keeps an index to the obj
I've just heard from another member of the client group and he cannot
reproduce the problem. I.e. he can install both the source package and
the binary that I sent out, without error.
So the problem seems to be in the system used by that first member of
the client group who contacted me.
I am developing a package ("ldEst" --- lethal dose estimation) for a
group of consulting clients. (The package may in the future be released
upon the unsuspecting public, but for the moment it has to stay
confidential, sad to say.)
The clients run Windoze (sad to say). In the past I have
