On Posit Workbench, pak does not use binaries even if binaries should be available in theory (PPM setup). We use a private instance of PPM, but I also get this behaviour for the public PPM:
> pak::system_r_platform()
[1] "x86_64-pc-linux-gnu-ubuntu-22.04"
> getOption("repos")
CRAN
"https://packagemanager.posit.co/cran/__linux__/jammy/latest"
> pak::meta_list("glue")[["sources"]]
[[1]]
[1] "https://packagemanager.posit.co/cran/__linux__/jammy/latest/src/contrib/glue_1.8.1.tar.gz"
> pak::meta_list("fs")[["platform"]]
[1] "source"
> pak::cache_clean()
> pak::pkg_install("glue")
✔ Loading metadata database ... done
→ Will install 1 package.
→ Will download 1 package with unknown size.
+ glue 1.8.1 [bld][cmp][dl]
ℹ Getting 1 pkg with unknown size
✔ Got glue 1.8.1 (source) (173.80 kB)
✔ Downloaded 1 package (173.80 kB) in 1.2s
ℹ Building glue 1.8.1
✔ Built glue 1.8.1 (388ms)
✔ Installed glue 1.8.1 (1.2s)
✔ 1 pkg: added 1, dld 1 (173.80 kB) [7.5s]
pak_siterep():
> pak::pak_sitrep()
* pak version:
- 0.9.4
* Version information:
- pak platform: x86_64-pc-linux-gnu (current: x86_64-pc-linux-gnu, compatible)
- pak repository: - (local install?)
* Optional packages installed:
- pillar
* Library path:
- /nfs-data/rhome/rgi/R/x86_64-pc-linux-gnu-library/4.5
- /opt/R/4.5.2/lib/R/library
* pak is installed at /nfs-data/rhome/rgi/R/x86_64-pc-linux-gnu-library/4.5/pak.
* Dependency versions:
- callr 3.7.6
- cli 3.6.6
- curl 5.2.3
- desc 1.4.3
- filelock 1.0.3
- jsonlite 2.0.0
- keyring 1.4.1
- lpSolve 5.6.23
- pkgbuild 1.4.8
- pkgcache 2.2.5.9000
- pkgdepends 0.9.1.9000
- pkgsearch 3.1.5
- processx 3.8.7
- ps 1.9.2
- R6 2.5.1
- yaml 2.3.12
- zip 2.3.3
* Dependencies can be loaded
On Posit Workbench, pak does not use binaries even if binaries should be available in theory (PPM setup). We use a private instance of PPM, but I also get this behaviour for the public PPM:
pak_siterep():