repoPrefix

Get the path to the repo directory containing the package files.

internal

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. The user can then install packages from this repository directly,
rather than from CRAN.  This is useful in production settings, e.g. server
behind a firewall, or remote locations with slow (or zero) Internet access.

Andrie Vries

miniCRAN

Create a Mini Version of CRAN Containing Only Selected Packages

Andrie de Vries

Alex Chubaty

Microsoft Corporation 

repoPrefix function

<dl><dt>type</dt>
<dd>character, indicating the type of package to download and
install. See <code><a href="/link/install.packages()?package=miniCRAN&version=0.3.0" data-mini-rdoc="miniCRAN::install.packages()">install.packages()</a></code>.</dd>
<dt>Rversion</dt>
<dd>Version of R (only used if <code>type</code> is not <code>source</code>.) Defaults to <a href="/link/R.version?package=miniCRAN&version=0.3.0" data-mini-rdoc="miniCRAN::R.version">R.version</a>, but this can be specified as any of the following formats:<ul>
<li>a character string with the two digit R version, e.g. "3.1"</li>
<li>a list with components <code>major</code> and <code>minor</code></li>
<li>the result of <code><a href="/link/getRversion()?package=miniCRAN&version=0.3.0" data-mini-rdoc="miniCRAN::getRversion()">getRversion()</a></code></li>
<li>the result of <a href="/link/R.version?package=miniCRAN&version=0.3.0" data-mini-rdoc="miniCRAN::R.version">R.version</a></li>
</ul></dd></dl>

Arguments

A repository has two main folders, one for source packages, and the other
for binary packages. Inside the binary package folder, <code>bin</code>, you will find
subfolders for Windows as well as the various OSX binaries.
<code>+- Root</code>
<code>...+- src/contrib</code>
<code>......+- PACKAGES</code>
<code>..+- bin</code>
<code>.......+- windows/contrib/version</code>
<code>..........+- PACKAGES</code>
<code>.......+- macosx/contrib/version</code>
<code>..........+- PACKAGES</code>
<code>.......+- macosx/mavericks/contrib/version</code>
<code>..........+- PACKAGES</code>
<code>.......+- macosx/leopard/contrib/version</code>
<code>..........+- PACKAGES</code>

Repo folder structure

Get the path to the repo directory containing the package files. — repoPrefix

<dl>

<dt>type</dt>
<dd>character, indicating the type of package to download and
install. See <code><a href='https://rdrr.io/r/utils/install.packages.html'>install.packages()</a></code>.</dd>


<dt>Rversion</dt>
<dd>Version of R (only used if <code>type</code> is not <code>source</code>.) Defaults to <a href='https://rdrr.io/r/base/Version.html'>R.version</a>, but this can be specified as any of the following formats:<ul>
<li>a character string with the two digit R version, e.g. "3.1"</li>
<li>a list with components <code>major</code> and <code>minor</code></li>
<li>the result of <code><a href='https://rdrr.io/r/base/numeric_version.html'>getRversion()</a></code></li>
<li>the result of <a href='https://rdrr.io/r/base/Version.html'>R.version</a></li>
</ul></dd>

</dl>

A repository has two main folders, one for source packages, and the other
for binary packages. Inside the binary package folder, <code>bin</code>, you will find
subfolders for Windows as well as the various OSX binaries.
<code>+- Root</code>
<code>...+- src/contrib</code>
<code>......+- PACKAGES</code>
<code>..+- bin</code>
<code>.......+- windows/contrib/version</code>
<code>..........+- PACKAGES</code>
<code>.......+- macosx/contrib/version</code>
<code>..........+- PACKAGES</code>
<code>.......+- macosx/mavericks/contrib/version</code>
<code>..........+- PACKAGES</code>
<code>.......+- macosx/leopard/contrib/version</code>
<code>..........+- PACKAGES</code>

repoPrefix: Get the path to the repo directory containing the package files.

Description

Usage

Value

Arguments

Repo folder structure