The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

fscache: File System Cache

Manages a file system cache. Regular files can be moved or copied to the cache folder. Sub-folders can be created in order to organize the files. Files can be located inside the cache using a glob function. Text contents can be easily stored in and retrieved from the cache using dedicated functions. It can be used for an application or a package, as a global cache, or as a per-user cache, in which case the standard OS user cache folder will be used (e.g.: on Linux $HOME/.cache/R/my_app_or_pkg_cache_folder).

Version: 1.0.5
Depends: R (≥ 4.1)
Imports: R.utils, R6, chk, lgr, lifecycle, stringi, tools
Suggests: covr, knitr, lintr, rmarkdown, roxygen2, stringr, testthat (≥ 2.0.0)
Published: 2024-06-02
DOI: 10.32614/CRAN.package.fscache
Author: Pierrick Roger ORCID iD [aut, cre]
Maintainer: Pierrick Roger <pierrick.roger at cea.fr>
BugReports: https://gitlab.com/cnrgh/databases/r-fscache/-/issues
License: AGPL-3
URL: https://gitlab.com/cnrgh/databases/r-fscache
NeedsCompilation: no
Materials: README
CRAN checks: fscache results

Documentation:

Reference manual: fscache.pdf
Vignettes: Introduction to fscache package

Downloads:

Package source: fscache_1.0.5.tar.gz
Windows binaries: r-devel: fscache_1.0.5.zip, r-release: fscache_1.0.5.zip, r-oldrel: fscache_1.0.5.zip
macOS binaries: r-release (arm64): fscache_1.0.5.tgz, r-oldrel (arm64): fscache_1.0.5.tgz, r-release (x86_64): fscache_1.0.5.tgz, r-oldrel (x86_64): fscache_1.0.5.tgz
Old sources: fscache archive

Reverse dependencies:

Reverse imports: sched

Linking:

Please use the canonical form https://CRAN.R-project.org/package=fscache to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.