Package: getaca 0.1.6

getaca: Reproducible External Data Dependencies

Declares, retrieves, verifies, tracks and actively manages external data dependencies too large or too fast-moving to ship inside a package. Resources are identified by package, name and version, pinned to a Secure Hash Algorithm (SHA-256) checksum, and resolved through an explicit policy so that the same installed package always resolves the same bytes. A registry served from a remote host may be signed with Ed25519 and verified against a key the declaring package ships, so the declaration and the key that vouches for it arrive by different routes. Hashing follows National Institute of Standards and Technology (2015) "Secure Hash Standard" <doi:10.6028/NIST.FIPS.180-4>; signing follows Bernstein, Duif, Lange, Schwabe and Yang (2012) "High-Speed High-Security Signatures" <doi:10.1007/s13389-012-0027-1> and Josefsson and Liusvaara (2017) "Edwards-Curve Digital Signature Algorithm (EdDSA)" <doi:10.17487/RFC8032>. Designed for reproducible offline use and graceful behaviour during package checks.

Authors:Gilles Colling [aut, cre, cph], Daniel J. Bernstein [ctb], Bernard van Gastel [ctb], Wesley Janssen [ctb], Tanja Lange [ctb], Peter Schwabe [ctb], Sjaak Smetsers [ctb]

getaca_0.1.6.tar.gz
getaca_0.1.6.zip(r-4.7-x86_64)getaca_0.1.6.zip(r-4.7-arm64)getaca_0.1.6.zip(r-4.6-x86_64)getaca_0.1.6.zip(r-4.6-arm64)getaca_0.1.6.zip(r-4.5-x86_64)
getaca_0.1.6.tgz(r-4.6-x86_64)getaca_0.1.6.tgz(r-4.6-arm64)getaca_0.1.6.tgz(r-4.5-x86_64)getaca_0.1.6.tgz(r-4.5-arm64)
getaca_0.1.6.tar.gz(r-4.7-arm64)getaca_0.1.6.tar.gz(r-4.7-x86_64)getaca_0.1.6.tar.gz(r-4.6-arm64)getaca_0.1.6.tar.gz(r-4.6-x86_64)
getaca_0.1.6.tgz(r-4.6-emscripten)
manual.pdf |manual.html✨
DESCRIPTION |NEWS
card.svg |card.png
getaca/json (API)

# Install 'getaca' in R:
install.packages('getaca', repos = c('https://gcol33.r-universe.dev', 'https://cloud.r-project.org'))

Bug tracker:https://github.com/gcol33/getaca/issues

Pkgdown/docs site:https://gillescolling.com

On CRAN:

Conda:

cachingchecksumdata-managementreproducibility

5.38 score 1 stars 12 scripts 259 downloads 37 exports 1 dependencies

Last updated from:7c970e80cb. Checks:15 OK. Indexed: yes.

TargetResultTimeFilesSyslog
linux-devel-arm64OK97
linux-devel-x86_64OK130
source / vignettesOK163
linux-release-arm64OK101
linux-release-x86_64OK119
macos-release-arm64OK90
macos-release-x86_64OK249
macos-oldrel-arm64OK94
macos-oldrel-x86_64OK226
windows-devel-arm64OK215
windows-devel-x86_64OK111
windows-release-arm64OK200
windows-release-x86_64OK96
windows-oldrel-x86_64OK112
wasm-releaseOK92

Exports:as_registryauth_hostbasicbearercombinergetacagetaca_availablegetaca_cache_dirgetaca_cataloguegetaca_cleangetaca_credentialsgetaca_infogetaca_keepgetaca_optionalgetaca_pingetaca_policygetaca_prefetchgetaca_progressgetaca_refreshgetaca_skip_if_unavailablepartprocessorregistryregistry_digestregistry_draftregistry_forregistry_keygenregistry_manifestregistry_readregistry_signregistry_verifyregistry_writereporterresolve_resourceresourceresource_idunpack

Dependencies:curl

Choosing Between getaca and the Alternatives
Installation | Bundling the data in the package | A companion data package | pins | BiocFileCache | pooch | A downloader and a cache directory | Targets and the workflow tools | renv | Decision summary | What getaca deliberately does not do | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

Declaring Resources
Installation | Records and channels | Anatomy of a record | Drafting from where the data is | Assembling the registry | Naming the channel head | Choosing current | Derived artefacts | Files that arrive in parts | Combining by something other than concatenation | A series that keeps growing | Processors | Writing your own | Authoring in YAML | Handing errors to your users | Hosting | Data behind a registration | Testing your declaration | Before you ship

Last update: 2026-10-10
Started: 2026-07-26

Handling Failures
Installation | The general shape | getaca_error_unavailable | getaca_error_offline | getaca_error_incomplete | getaca_error_credentials | getaca_error_upstream_changed | getaca_error_declaration | getaca_error_composition | getaca_error_cache_corrupt | getaca_error_redeclared | getaca_error_invalid_registry | getaca_error_signature | Writing a handler in a declaring package | Testing your handlers | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

Migrating an Existing Downloader
Installation | What is being replaced | Step 1: turn the URL table into records | Step 2: assemble and ship the registry | Step 3: rewrite the front door | Step 4: replace the guards | Step 5: retire the version guesswork | Handling users who already have the old cache | The migration, as a checklist | What the migration bought | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

Policies and Channels
Installation | The two halves the design keeps apart | bundled | current | What a remote channel may change | Moving the head | Signing a remote channel | pinned | Pins and renv | offline | How the policy in force is decided | Choosing a default as an author | What is recorded | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

Quick Start
Installation | Declaring what you need | Getting it | Which version a bare name resolves to | Surviving R CMD check | When it does not work | Knowing where a file came from | Where things are stored | Choosing a policy | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

Surviving R CMD check and CI
Installation | The check clamp | The three helpers | In tests | In examples | In vignettes | Anywhere a logical reads better | Seeding a cache | GitHub Actions | A separate job for the expensive path | Testing that the guards work | Reproducing a check machine locally | When the check farm disagrees with your CI | What a check run actually does | What to say in DESCRIPTION | CRAN checklist | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

The Cache
Installation | Where it lives | Layout | What a cached copy has to prove | Provenance | Two sessions, one download | How bytes get in | Watching a transfer | Retention | Cleaning by hand | Settings | Moving a cache | Where to go next

Last update: 2026-10-10
Started: 2026-07-26

Readme and manuals

Help Manual

Help pageTopics
Convert an authoring format into a registryas_registry
Declare how parts are combinedcombiner
Get a declared external resourcegetaca
Where getaca stores thingsgetaca_cache_dir
What is declared, and what is cachedgetaca_catalogue
Which credentials a package expectsgetaca_credentials
Provenance for a resourcegetaca_info
Keep a resource from being collectedgetaca_keep
Freeze current resolution into a pin filegetaca_pin
Resolution policy and settingsgetaca_policy
Warm the cache ahead of timegetaca_prefetch
Choose how transfers report progressgetaca_progress
Forget cached registry stategetaca_refresh
Declaring a credential without holding oneauth_host basic bearer getaca-auth
Behave during checks, examples and testsgetaca-checks getaca_available getaca_optional getaca_skip_if_unavailable
Active cache managementgetaca-gc getaca_clean
How a transfer reports itselfgetaca-progress
Declare one part of a resourcepart
Declare a post-download processorprocessor
Declare a package's external resourcesregistry
Content identity of a registryregistry_digest
Draft a registry from where the data isregistry_draft
Find the registry a package shipsregistry_for
Create a signing keyregistry_keygen
The canonical form a registry hashes toregistry_manifest
Sign a registry fileregistry_sign
Verify a signed registry fileregistry_verify
Read and write registry filesregistry_read registry_write
Write a progress reporterreporter
Resolve a name to an immutable resource recordresolve_resource
Declare an immutable resource recordresource
Identify a resourceresource_id
Unpack an archive or a compressed fileunpack