upgrade=FALSE is not passed through to dependent installations #53
Comments
|
👍 |
jimhester
added a commit
to jimhester/remotes
that referenced
this issue
Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes and dependencies. This means you can supply the authentication in in the top level `install_()` call and have that same authentication be used in downstream Remotes. This also should propagate upgrade to dependencies appropriately, so setting `upgrade = FALSE` should disable upgrading for all dependencies, even grandchildren. Fixes r-lib#86 Fixes r-lib#53
jimhester
added a commit
to jimhester/remotes
that referenced
this issue
Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes and dependencies. This means you can supply the authentication in in the top level `install_()` call and have that same authentication be used in downstream Remotes. This also should propagate upgrade to dependencies appropriately, so setting `upgrade = FALSE` should disable upgrading for all dependencies, even grandchildren. Fixes r-lib#86 Fixes r-lib#53
jimhester
added a commit
to jimhester/remotes
that referenced
this issue
Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes and dependencies. This means you can supply the authentication in in the top level `install_()` call and have that same authentication be used in downstream Remotes. This also should propagate upgrade to dependencies appropriately, so setting `upgrade = FALSE` should disable upgrading for all dependencies, even grandchildren. Fixes r-lib#53 Fixes r-lib#86 Fixes r-lib#87
jimhester
added a commit
to jimhester/remotes
that referenced
this issue
Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes and dependencies. This means you can supply the authentication in in the top level `install_()` call and have that same authentication be used in downstream Remotes. This also should propagate upgrade to dependencies appropriately, so setting `upgrade = FALSE` should disable upgrading for all dependencies, even grandchildren. Fixes r-lib#53 Fixes r-lib#86 Fixes r-lib#87
jimhester
added a commit
to jimhester/remotes
that referenced
this issue
Aug 29, 2018
We now pass all authentication arguments and build arguments to remotes and dependencies. This means you can supply the authentication in in the top level `install_()` call and have that same authentication be used in downstream Remotes. This also should propagate upgrade to dependencies appropriately, so setting `upgrade = FALSE` should disable upgrading for all dependencies, even grandchildren. Fixes r-lib#53 Fixes r-lib#86 Fixes r-lib#87
jimhester
added a commit
that referenced
this issue
Aug 31, 2018
We now pass all authentication arguments and build arguments to remotes and dependencies. This means you can supply the authentication in in the top level `install_()` call and have that same authentication be used in downstream Remotes. This also should propagate upgrade to dependencies appropriately, so setting `upgrade = FALSE` should disable upgrading for all dependencies, even grandchildren. Fixes #53 Fixes #86 Fixes #87
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrading packages tends to lead to really broken sets of packages on windows due to file locking, and so I tend to set
upgrade = FALSEquite a lot (I would love aremotes.upgradeglobal option that I could set to FALSE).If a package installed by
remotes::install_githublists a remote in its description then subsequent installations do not honour theupgrade = FALSEargumentThe text was updated successfully, but these errors were encountered: