-
Notifications
You must be signed in to change notification settings - Fork 3
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
Confirm pak is picking up packages from DownloadURL #87
Comments
I tried with |
It seems that the functions After examining the source code of pak, it seems that all downloading activities are handled via R6 methods of a Inspecting the internal operations of pak is challenging due to the encapsulation of processes within callr/processx subprocesses. Additionally, the private methods of the R6 classes do not facilitate quick reviews. I also searched for any references to the Perhaps consulting @gaborcsardi directly might be the quickest approach. :) |
You can check the summary that pak returns. E.g. this container installs from a repo at GH releases: istats <- pak::pkg_install("pillar")
> names(istats)
[1] "ref" "type" "direct"
[4] "directpkg" "status" "package"
[7] "version" "license" "needscompilation"
[10] "priority" "md5sum" "sha256"
[13] "filesize" "built" "platform"
[16] "rversion" "repotype" "repodir"
[19] "target" "deps" "mirror"
[22] "sources" "remote" "error"
[25] "metadata" "dep_types" "params"
[28] "sysreqs" "os_type" "cache_status"
[31] "sysreqs_packages" "sysreqs_pre_install" "sysreqs_post_install"
[34] "sysreqs_install" "lib_status" "old_version"
[37] "new_version" "fulltarget" "fulltarget_tree"
[40] "download_status" "download_error" "file_size"
[43] "library" "binary" "dependencies"
[46] "installed" "vignettes" "install_args"
[49] "packaged" "file" "package_done"
[52] "package_time" "package_error" "package_stdout"
[55] "build_done" "build_time" "build_error"
[58] "build_stdout" "install_done" "install_time"
[61] "install_error" "install_stdout" "worker_id"
[64] "deps_left"
istats[, c("package", "sources")]
Is this what you need? |
Thank you Gábor! I had noticed that the output of pak::pkg-install() did indeed included the sources but it has been difficult to actually confirm that that URL is the one used for the download. |
Following up on #74
@borgmaan mentioned today that we need to confirm that the packages being installed from the url specified in the
PACKAGES
DownloadURL
after setting a repo to a local file path as shown in https://github.com/pharmaR/repos/blob/feature/riskscore/dev/merge-riskscore.RThere are probably plenty of ways of testing this. One idea is to
debugonce(download.file); debugonce(download.package)
. I'm not certain these are used on the backend, but I think they're probably a safe bet.tagging @ramiromagno for interest
The text was updated successfully, but these errors were encountered: