Closed ediferreira11 closed 2 months ago
Remotes: pkg123=git::https://devops-org-name/project-name/_git/pkg123_release
seems to work for me with the dev version of remotes.
Oh, I'm sorry, I focused so much on pak
that I didn't notice I was not using the latest version of remotes
. I was on 1.2.4.1 instead of 1.2.5. I will close this issue. Thank you very much for your help!
Let me just add that maybe it makes sense to add that it is now possible to add the package name on the vignette for remotes
(https://remotes.r-lib.org/articles/dependencies.html), even though it has no effect on how it works
Hello,
So far we've been using the
remotes
package at the company to install our internal packages from Azure DevOps. However, there are some things that haven't been as smooth as I would like and today I was testingpak
.Everything seems to work just fine (great work btw), except the
Remotes
field on theDESCRIPTION
file. I've read on your documentation that when agit::
entry does not end with the package name (e.g.r-pins
), we need to addr-pins=
before thegit::
tag. Even though it is true that this works, that means that when trying to install the package usingremotes::install_git()
, the installation fails because it doesn't recognize that prefix.Example below:
For a package named
pkg123
(where the repo is calledpkg123_release
), the example above would work with theremotes
package, but it wouldn't work withpak
.If I change the Remotes to
pkg123=git::https://devops-org-name/project-name/_git/pkg123_release
now I have the opposite problem, it works forpak
but it fails usingremotes
with the following message:Is there anyway to make it compatible with both packages without changing the repository names? I'm asking because I believe some people will still use
remotes::install_git()
which would no longer work with the changes.Thank you! I know this is not a reprex but hopefully it is clear enough.