devxy/build-cran-binaries
Watch
1
0
Fork
You've already forked build-cran-binaries
 0
Code Issues 12 Pull requests Releases Activity

docs: drop stale references to the cranlike fork

Browse source 
- explain GITHUB_PAT by bincraft's DESCRIPTION reads from the CRAN mirror
- describe how upload_package_index() builds the index in the README
This commit is contained in:
Patrick Schratz 2026-10-17 14:11:12 +00:00
commit cbe538f351
No known key found for this signature in database
GPG key ID: 62050D5BC68AB6DC
1 changed files with 21 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -103,11 +103,13 @@ Preview the selection without building or accessing storage or build metadata:
### Creating/Updating the PACKAGES Index Files
Currently, the {cranlike} and {desc} packages only work with files on a local file system.
Tools such as `tools::write_PACKAGES()` and {cranlike} only index files on a local file system.
This is infeasible if the goal is to store binaries in S3.
Storing binaries permanently on a disk-based file system would incur significantly higher costs, especially when operating in the cloud.
Hence, [{cranlike}](https://devxy.gitlab.io/r-package-binaries/bincraft/) and [{desc}](https://github.com/pat-s/desc/tree/description-from-remote) were forked to handle files in S3 (through {s3fs}).
Hence, `bincraft::upload_package_index()` builds the index from a listing of the slot in S3 (through {s3fs}).
Each record is read from the package's CRAN `DESCRIPTION` on the GitHub mirror of CRAN, falling back to the `DESCRIPTION` inside the tarball for a package the mirror does not have.
The previously published `PACKAGES.rds` serves as a cache, so only new or replaced tarballs are read.
### Resources