Closed tblazina closed 5 years ago
Hey @tblazina, you can use jetpack::update("futile.logger")
for this.
Thanks @ankane, after I run jetpack::update("futile.logger")
it seems to still be using the latest release of futile.logger
and doesn't include all the code (e.g. I'm trying to use their appender.file2()
function). Jetpack gives the message after the update: Updated futile.logger to 1.4.3 (was 1.4.3)
.
Does your packrat.lock
have GitHub as the source for futile.logger, as well as the latest SHA? The version on GitHub is 1.4.3, so the update message will still say that.
Closing due to no response
I am wondering if there is a way to have jetpack use the latest changes in a specific repo. I know you can use
jetpack::add("somepackage", remote="someauthor/somepackage")
but this seems to be using the latest release.For example,
futile.logger
(https://github.com/zatonovo/futile.logger) is on release v.1.4.3 and indeed when I usejetpack::add("futile.logger", remote="zatonovo/futile.logger")
this version is installed and added to theDESCRIPTION
andpackrat.lock
files, however the repo has changes which they haven't created a release for yet and I am wondering if it is possible to specify this usingjetpack
?Thanks a lot for the great package btw!