Closed kendonB closed 4 years ago
This is expected. Package hashes are built from the DESCRIPTION file only.
You should bump your package version when you modify the package. Or, host your package on GitHub or another Git repository so that the commit hash can be used instead when hashing the package.
I see - might a future version of renv hash user packages like I thought?
This is unlikely to change.
One of the main constraints on the hashing function is that it must produce the same hash for the same package, regardless of the machine. This implies that the same package installed on macOS, Linux, or Windows needs to have the same hash. Otherwise, in collaborative scenarios, the lockfile hashes would change every time someone on a different OS tried to snapshot the project!
@wlandau see above. Would an extension to drake's approach to code hashing work for R packages as a whole? I'm guessing it would have to be comprehensive including compiled code and possibly docs for renv
.
Looks like the hashes aren't getting obeyed when it comes to local package changes:
Created on 2019-11-21 by the reprex package (v0.3.0)