miniCRAN | R package to create | Build Tool library

by andrie R Version: v0.2.13 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | miniCRAN Summary

miniCRAN is a R library typically used in Utilities, Build Tool applications. miniCRAN has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

At the end of 2014, CRAN consisted of more than 6,000 packages, and by 2017 this number doubled to more than 12,000. Many organisations need to maintain a private mirror of CRAN, but with only a subset of packages that are relevant to them. The miniCRAN package makes it possible to create an internally consistent repository consisting of selected packages from CRAN-like repositories. The user specifies a set of desired packages, and miniCRAN recursively reads the dependency tree for these packages, then downloads only this subset.

Support

Quality

Security

License

Reuse

Support

miniCRAN has a low active ecosystem.

It has 128 star(s) with 40 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 14 open issues and 106 have been closed. On average issues are closed in 631 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of miniCRAN is v0.2.13

Quality

miniCRAN has 0 bugs and 0 code smells.

Security

miniCRAN has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

miniCRAN code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

miniCRAN is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

miniCRAN releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 1107 lines of code, 0 functions and 3 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of miniCRAN

Get all kandi verified functions for this library.

miniCRAN Key Features

No Key Features are available at this moment for miniCRAN.

miniCRAN Examples and Code Snippets

No Code Snippets are available at this moment for miniCRAN.

Community Discussions

Trending Discussions on miniCRAN

R script: Installing packages from offline miniCRAN, still tries to access internet

How to automatically install Bioconductor package on which a CRAN package depends through a long chain of dependencies?

QUESTION

R script: Installing packages from offline miniCRAN, still tries to access internet

Asked 2021-Nov-16 at 09:40

I need to install multiple R packages on a server with restricted internet access, i.e all cran repositories are blocked. I created an offline miniCRAN repository which also includes dependencies which made it seem like a perfect fit.

The problem is that it seems like R makes calls with https to the local source folder to fetch it. And that seems to be blocked as well on the server.

How do I prevent the installation from accessing the local packages through http calls?

(This process works on a similar server without the same network restrictions)

...

ANSWER

Answered 2021-Nov-16 at 09:40

My bad. The script should look like this:

Source https://stackoverflow.com/questions/69986000

QUESTION

How to automatically install Bioconductor package on which a CRAN package depends through a long chain of dependencies?

Asked 2020-Jun-20 at 20:24

I have a package metagam which is on CRAN, and it passes all of CRAN's automated tests. However, the package depends on the Bioconductor package multtest through the chain of dependencies metagam <- metap <- mutoss <- multtest. This is visualized below for the dependencies of the metap package.

...

ANSWER

Answered 2020-Jun-20 at 14:40

Because Bioconductor has twice-yearly releases, and this differs from CRAN release practices, the 'right' thing to do is to use Bioconductor tools to install your package, so BiocManager::install("metap"). It does not matter that metap is a CRAN package. BiocManager installs the correct version of the Bioconductor package for the user's version of R.

If this solution isn't palatable, then the next-best right thing to do is to adjust your dependencies to avoid direct or indirect dependencies on Bioconductor packages.

Source https://stackoverflow.com/questions/62486902

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install miniCRAN

You can download it from GitHub.

Support

I started this project while employed by Revolution Analytics and Microsoft. Microsoft has kindly agreed that I maintain the project individually, and retains copyright to all work on the project until October 2017.

Find more information at: