From: *R-package-devel on
behalf
of Greg Hunt
*Date: *Sunday, March 31, 2024 at 7:35 AM
*To: *Dirk Eddelbuettel
*Cc: *List r-package-devel
*Subject: *Re: [R-pkg-devel] Order of repo access from options("repos")
Dirk,
Sadly I can't use localhost for all of those. 172.17.0.1
On 02.04.2024 14:07, Dirk Eddelbuettel wrote:
On 1 April 2024 at 17:44, Uwe Ligges wrote:
| Untested:
|
| install.packages() calls available.packages() to find out which packages
| are available - and passes a "filters" argument if supplied.
| That can be a user defined filter. It should be po
gt;
> >>
> >>
> >> By default, the return value includes only packages whose version
> >>
> >> and OS requirements are met by the running version of R, and only
> >>
> >> gives information on the latest versions of packag
d then the result filtered to contain
just the most recent version of each. Does it matter then what order the
repositories are visited?
Martin Morgan
*From: *R-package-devel on behalf
of Greg Hunt
*Date: *Sunday, March 31, 2024 at 7:35 AM
*To: *Dirk Eddelbuettel
*Cc: *List r-package-deve
On 1 April 2024 at 17:44, Uwe Ligges wrote:
| Untested:
|
| install.packages() calls available.packages() to find out which packages
| are available - and passes a "filters" argument if supplied.
| That can be a user defined filter. It should be possible to write a user
| defined filter which
ost recent version of each. Does it matter then what order the
repositories are visited?
Martin Morgan
*From: *R-package-devel on behalf
of Greg Hunt
*Date: *Sunday, March 31, 2024 at 7:35 AM
*To: *Dirk Eddelbuettel
*Cc: *List r-package-devel
*Subject: *Re: [R-pkg-devel] Order of repo acc
st recent version of each. Does it matter then what order the
> repositories are visited?
>
>
>
> Martin Morgan
>
>
>
> *From: *R-package-devel on behalf
> of Greg Hunt
> *Date: *Sunday, March 31, 2024 at 7:35 AM
> *To: *Dirk Eddelbuettel
> *Cc: *List
It may also be useful to use:
options(internet.info = 1)
to get more information on the web requests R is making. (See the
documentation in ?options for more details.)
Looking at the source code in available.packages, R does iterate
through the repositories in the same order they're provided
On 31 March 2024 at 11:43, Martin Morgan wrote:
| So all repositories are consulted and then the result filtered to contain just
| the most recent version of each. Does it matter then what order the
| repositories are visited?
Right. I fall for that too often, as I did here. The order matters f
of repo access from options("repos")
Dirk,
Sadly I can't use localhost for all of those. 172.17.0.1 is an internal
Docker IP, not the localhost address (127.0.0.1), they are there to handle
two different scenarios and different ones will fail to resolve in
different scenarios. Are
Dirk,
Sadly I can't use localhost for all of those. 172.17.0.1 is an internal
Docker IP, not the localhost address (127.0.0.1), they are there to handle
two different scenarios and different ones will fail to resolve in
different scenarios. Are you saying that the DNS lookup adds a timing
issue t
Greg,
There are AFAICT two issues here: how R unrolls the named vector that is the
'repos' element in the list 'options', and how your computer resolves DNS for
localhost vs 172.17.0.1. I would try something like
options(repos = c(CRAN = "http://localhost:3001/proxy";,
When I set multiple repositories in options(repos=...) the order of access
is providing me with some surprises as I work through some CICD issues:
Given:
options(
repos = c(
CRAN = "http://localhost:3001/proxy";,
C = "http://172.17.0.1:3002";,
B = "http://172.17.0.1:3001/proxy";
13 matches
Mail list logo
