Good day,
Indeed, the setting of .libPaths() would avoid the error shown by the example.
But, it seems unintuitive that R tries to load a package from one directory and
its dependencies from another if the dependency is present in the same library
as the package being loaded by the user's libra
On 07/25/2018 04:28 AM, Uwe Ligges wrote:
Not sure if this is a bug: where is it documented that this works not
as above (which is what I would expect)?
The documentation doesn't say one way or the other. But the fact remains
that base:::.getRequiredPackages2, when provided a non-null lib.lo
On 25.07.2018 04:00, Dario Strbenac wrote:
Good day,
A self-contained example which reproduces the problem is
packagesFolder <- tempdir()
latestFolder <- file.path(packagesFolder, "latest")
dir.create(latestFolder)
devtools::create(file.path(latestFolder, "statistics"), description = list(V
On 24.07.2018 23:37, Benjamin Tyner wrote:
On 07/24/2018 07:50 AM, Martin Maechler wrote:
Benjamin Tyner
on Sat, 21 Jul 2018 13:42:43 -0400 writes:
> Not sure whether it is the same issue as was raised here:
> https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html
Good day,
A self-contained example which reproduces the problem is
packagesFolder <- tempdir()
latestFolder <- file.path(packagesFolder, "latest")
dir.create(latestFolder)
devtools::create(file.path(latestFolder, "statistics"), description =
list(Version = "1.1.0", Depends = "extras (>= 1.0.5)"
On 07/24/2018 07:50 AM, Martin Maechler wrote:
Benjamin Tyner
on Sat, 21 Jul 2018 13:42:43 -0400 writes:
> Not sure whether it is the same issue as was raised here:
> https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html
> but in any case perhaps the problem cou
> Benjamin Tyner
> on Sat, 21 Jul 2018 13:42:43 -0400 writes:
> Not sure whether it is the same issue as was raised here:
> https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html
> but in any case perhaps the problem could partially be remedied on line
> 245
Good day,
Now that I read about Renaud's problem, I realise that it is effectively the
same as mine.
--
Dario Strbenac
University of Sydney
Camperdown NSW 2050
Australia
__
R-devel@r-project.org mailing list
https://
Not sure whether it is the same issue as was raised here:
https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html
but in any case perhaps the problem could partially be remedied on line
245 of src/library/base/R/library.R by passing the lib.loc to
.getRequiredPackages2() ...here is a p
> Benjamin Tyner
> on Fri, 20 Jul 2018 19:42:09 -0400 writes:
> Here's a trick/workaround; if lib.loc is the path to your
> library, then prior to calling library(),
>> environment(.libPaths)$.lib.loc <- lib.loc
Well, that is quite a "trick" -- and potentially a pretty
Here's a trick/workaround; if lib.loc is the path to your library, then
prior to calling library(),
> environment(.libPaths)$.lib.loc <- lib.loc
Good day,
If there's a library folder of the latest R packages and a partic
Good day,
If there's a library folder of the latest R packages and a particular package
from it is loaded using the lib.loc option, the dependencies of that package
are still attempted to be loaded from another folder of older packages
specified by R_LIBS, which may cause errors about version r
12 matches
Mail list logo
