Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/ropensci/software-review/issues/6 below:

rrlite · Issue #6 · ropensci/software-review · GitHub

• 1. What does this package do? (explain in 50 words or less)
     This package provides an interface to "rlite" - a standalone, zero-configuration port of the Redis interface (rlite is to Redis what sqlite is to MySQL).
• 1. Paste the full DESCRIPTION file inside a code block (bounded by ``` on either end).

Package: rrlite
Title: R bindings to rlite
Version: 0.1.0
Description: R bindings to rlite.  rlite is a "self-contained,
  serverless, zero-configuration, transactional redis-compatible
  database engine. rlite is to Redis what SQLite is to SQL.".
Depends: R (>= 3.1.2)
License: BSD_2_clause + file LICENSE
LazyData: true
Author: Rich FitzJohn
Maintainer: Rich FitzJohn <rich.fitzjohn@gmail.com>
Suggests: testthat,
    knitr,
    RcppRedis
Imports: R6, Rcpp
LinkingTo: Rcpp
VignetteBuilder: knitr
SystemRequirements: GNU make

• 1. URL for the package (the development repository, not a stylized html page)
     https://github.com/richfitz/rrlite
• 1. What data source(s) does it work with (if applicable)?
     User-supplied, but arbitrary. Special support for data.frames. No direct support for existing remote data sources.
• 1. Who is the target audience?
     Package developers, technically minded users who need to process large data or scale analyses. This is a low-level package.
• 1. Check the box next to each policy below, confirming that you agree. These are mandatory.
• The repository has continuous integration with Travis and/or another service
• The package contains a vignette
• The package contains a reasonably complete readme with devtools install instructions
• The package contains unit tests
• 1. Do you agree to follow the rOpenSci packaging guidelines? These aren't mandatory, but we strongly suggest you follow them. If you disagree with anything, please explain.
• Are there any packages that your package depends on that are not on CRAN?
• Do you intend for this package to go on CRAN?
• Does the package have a CRAN accepted license?
• Did devtools::check() produce any errors or warnings? If so paste them below.

* checking for executable files ... WARNING
Found the following executable files:
  src/rlite/deps/lua/src/lua
  src/rlite/deps/lua/src/luac

(this can be fixed by uncommenting the cleanup script but that slows down local development and I've not worked out a good workflow there. Rbuildignore has proved difficult to use for this).

• 1. Please add explanations below for any exceptions to the above:
     Not covered in the requested information, but in it's current state, the package is highly unlikely to work under Windows. I'm holding off attempting with R this until the upstream rlite is confirmed to work. Once that's done, this package would definitely want appveyor support to ensure continued Windows compatibility.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4