Ran into this issue a few days ago---using pak conflicts with devtools::install() dependency resolution if you have previously used pak to install a dependency via a git URL. devtools tries to update packages listed in the DESCRIPTION "Remotes" tag via remotes::install_deps(), but fails because pak specified the RemoteType "git" and remotes does not recognize this type.
A related (the same?) issue was posted in #830, but I think this is a compatibility issue in remotes.
I recognize that we are in a transitional time of current best practices with pak, remotes, and devtools (#808), but I haven't seen info on the timeline for devtools is transitioning to pak (which would bypass this issue) so I am wondering if it is worth resolving this issue in remotes in the meantime. It seems like having remotes treat the RemoteType "git" identically to "xgit" would resolve the issue.
Ran into this issue a few days ago---using
pakconflicts withdevtools::install()dependency resolution if you have previously usedpakto install a dependency via a git URL.devtoolstries to update packages listed in the DESCRIPTION "Remotes" tag viaremotes::install_deps(), but fails becausepakspecified the RemoteType "git" andremotesdoes not recognize this type.A related (the same?) issue was posted in #830, but I think this is a compatibility issue in
remotes.I recognize that we are in a transitional time of current best practices with
pak,remotes, anddevtools(#808), but I haven't seen info on the timeline fordevtoolsis transitioning topak(which would bypass this issue) so I am wondering if it is worth resolving this issue inremotesin the meantime. It seems like havingremotestreat the RemoteType "git" identically to "xgit" would resolve the issue.