-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote dependencies are ignored #246
Comments
I can reproduce the issue, the problem seems to be that URL remotes don't have a package name and we are filtering remotes by the package name. I think the logic needs to be changed to keep remotes with a |
All URL remotes will have an NA package name, as there is no way to determine it without downloading the full package. Fixes r-lib#246
This should be fixed by #247 Please try installing it with remotes::install_github("r-lib/remotes#247") And testing it on your example to see if it fixes the issue. |
Or, if I already have
|
All URL remotes will have an NA package name, as there is no way to determine it without downloading the full package. Fixes r-lib#246
Please try installing from the PR again, I have pushed additional changes which should fix this. |
Working now! Thanks a tonne -- this will make managing our internal package dependencies so much better :) |
All URL remotes will have an NA package name, as there is no way to determine it without downloading the full package. Fixes r-lib#246
All URL remotes will have an NA package name, as there is no way to determine it without downloading the full package. Fixes r-lib#246
All URL remotes will have an NA package name, as there is no way to determine it without downloading the full package. Fixes #246
I have two packages hosted remotely, where
testpkg2
relies ontestpkg1
. Following this vignette, I listed the remote dependency under the "Remotes" section of my DESCRIPTION file. However, when installingtestpkg2
, it appears that no effort is made to install its remote dependencytestpkg1
.To be clear, my DESCRIPTION file for
testpkg2
looks like this:When I try to install it (without first installing
testpkg1
myself), I get an error:I also tried making a
testpkg3
which lists the same Remote dependency but does not include it under "Imports". i.e.:This installs fine, but does not also install
testpkg1
:In both cases, it appears that the "Remotes" section of my DESCRIPTION file is just completely ignored. Am I misinterpreting the vignette, or is this feature not actually implemented yet?
Note that I CAN install
testpkg2
succesfully if I first installtestpkg1
myself manually...but that seems to defeat the point:The text was updated successfully, but these errors were encountered: