Jim Hester

I guess alternatively we could do as you propose and use a namespaced call for the function, but that would require changing the remote specification.

My main concern with allowing extensibility is supporting it, in particular the internal generics used are not currently exported and it is possible we change how the internals work in...

I would suggest you use [pak](https://github.com/r-lib/pak) if you want this, it does use a solver to upgrade only what is needed to fulfill the requirements. We have no plans to...

I do not believe it would be a simple addition and I think it is out of scope for remotes, which is really a wrapper around `install.packages()`, which does not...

Yeah I think you are right, but it is good to capture the error message as well in an issue, thanks!

These are really bugs in `utils::untar()` / the R configuration, not really in remotes, but probably many people don't run into them because they never try to untar anything with...

`install.packages()` / `R CMD INSTALL` seem to essentially force the use of internal untar, maybe we should do the same... ```r if (utils::untar(pkg, exdir = tmpdir, tar = Sys.getenv("R_INSTALL_TAR", "internal")))...

in the linux case yes likely `TAR` is set to `/bin/gtar` on that system for some reason. On windows if `TAR` is unset it uses `Sys.which("tar.exe")`

We have seen this gtar issue with anaconda a couple other times, it seems quite long standing (and clearly others are running into this as well based on the upvotes)...

We can't do this in remotes, remotes can't have dependencies on third party packages.