miniCRAN icon indicating copy to clipboard operation
miniCRAN copied to clipboard

R package to create internally consistent, mini version of CRAN

Results 20 miniCRAN issues
Sort by recently updated
recently updated
newest added

hey there, When adding a package to a repo (or building it from a vector), it would be better if the function skipped the existing package. For example, adding {rlang}...

Idea

I tried the below but `makeRep` doesn't work for ARM macOS packages ``` download

Following up the discussion in #81, created a `deletePackage` functionality. Documentation and tests are included. Also spotted two minor inconsistencies in the existing code -- see diff for details. The...

Hello, Can the `UpdatePackages()` function take UNC paths as its path perimeter? I tried to pass a UNC path this way: ``` path = '\\\\sample-location.net\\repo; updatePackages(path = path, ...) ```...

bug
question

This is a feature that gets requested often Related to: - #23 new function to add a local package - #9 Add capability to read package data from local file...

enhancement
Idea
Epic

hello, I’m experiencing some issues when trying to addLocalPackage to a repository on a unc file path like so * `\\\\\\\\fileserver\\\\dir\\\\minicran\\\\`, or * `file.path('', '', 'fileserver', 'dir', 'minicran')`, or *...

While I was checking the versions in my repo with `checkVersions`, I was a bit surprised because I had done a good bit of processing to ensure there were no...

Resolved in branch

I am using 3.6.1 and building a miniCRAN for R 3.4.4. The new packages get added correctly and build a miniCRAN for R 3.4.4 correctly. However, when trying to install...

Resolved in branch

Managing a miniCRAN repo with multiple package types, I get the following warnings: ```r > updatePackages(..., type = c("mac.binary.el-capitan", "win.binary", "source"), ...) Warning messages: 1: In if (type == "both")...

If a new version of a package gets added to the repo, move the old version to the archive

enhancement