You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a package has already been installed, attempting to install it again with a broader set of dependencies has no effect. One would expect that the additional dependencies would be installed.
pak::pak("<remote>") # installs package and hard dependencies
pak::pak("<remote>", dependencies = TRUE) # will not install new dependencies if package is already installed
I had to do a double take because I was sure it was a Suggests dependency, but didn't go out and confirm. I was just chatting with the maintainer which prompted the bug report, and it looks like they made a commit to bump it to Imports to skirt this issue for now.
Thanks for continuing to investigate and following up with a more reproducible example. I'll add commit hashes to the original examples.
If a package has already been installed, attempting to install it again with a broader set of dependencies has no effect. One would expect that the additional dependencies would be installed.
Example
Using https://github.com/ddsjoberg/gtsummary as an example, which takes two remote dependencies:
Installing with
pak::pak("ddsjoberg/gtsummary@518be7d8")
, as expectedcards
gets installed, but notcardx
Then attempting to install with suggested dependencies using
pak::pak("ddsjoberg/gtsummary@518be7d8", dependencies = TRUE)
However, if I
remove.packages("gtsummary")
and try again:The text was updated successfully, but these errors were encountered: