Downloads:

117

Downloads of v 0.4.0:

18

Last Update:

30 May 2022

Package Maintainer(s):

Software Author(s):

  • Gábor Csárdi

Tags:

rig R rstats installer installation manager

rig

This is not the latest version of rig available.

  • 1
  • 2
  • 3

0.4.0 | Updated: 30 May 2022

Downloads:

117

Downloads of v 0.4.0:

18

Maintainer(s):

Software Author(s):

  • Gábor Csárdi

  • 1
  • 2
  • 3
rig 0.4.0

This is not the latest version of rig available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install rig, run the following command from the command line or from PowerShell:

>

To upgrade rig, run the following command from the command line or from PowerShell:

>

To uninstall rig, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade rig -y --source="'INTERNAL REPO URL'" --version="'0.4.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade rig -y --source="'INTERNAL REPO URL'" --version="'0.4.0'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install rig
  win_chocolatey:
    name: rig
    version: '0.4.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'rig' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.4.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller rig
{
    Name     = "rig"
    Version  = "0.4.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'rig':
  ensure   => '0.4.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator TheCakeIsNaOH on 06 Jun 2022.

Description

Install, remove, configure multiple R versions.

Features

  • Works on macOS, Windows and Linux (Ubuntu and Debian).
  • Install multiple R versions, select the default one.
  • Select R version to install using symbolic names: devel, next, release, oldrel, etc.
  • Run multiple versions at the same time using quick links. E.g. R-4.1 or R-4.1.2 starts R 4.1.x. Quick links are automatically added to the user’s path.
  • On M1 macs select between x86_64 and arm64 versions or R, or install both.
  • Creates and configures user level package libraries.
  • Restricts permissions to the system library. (On macOS, not needed on Windows and Linux).
  • Includes auto-complete for zsh and bash, on macOS and Linux.
  • Updates R installations to allow debugging with lldb, and to allow core dumps, on macOS.
  • Installs the appropriate Rtools versions on Windows and sets them up.
  • Cleans up stale R-related entries from the Windows registry.
  • Switches to root/administrator user as needed.

Feedback

Please open an issue in our issue tracker at https://github.com/r-lib/rig/issues


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  softwareName   = 'rig*'
  PackageName    = $env:ChocolateyPackageName
  FileType       = 'exe'
  SilentArgs     = '/VERYSILENT /SUPPRESSMSGBOXES'
  Url64bit       = 'https://github.com/r-lib/rig/releases/download/v0.4.0/rig-windows-0.4.0.exe'
  Checksum64     = '2080616af027d80f1d84e8d2ecf1a24b2e3afd624d2604832fe01ec724aac95d'
  ChecksumType64 = 'sha256'
}

Install-ChocolateyPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
rig 0.5.1 23 Tuesday, August 23, 2022 Approved
rig 0.5.0 30 Friday, June 17, 2022 Approved
rig 0.4.1 23 Saturday, June 11, 2022 Approved
rig 0.4.0 18 Monday, May 30, 2022 Approved

rig 0.4.0

NEW NAME

rim is now known as rig.

New features

  • Experimental multi-library support. See rig library --help for the
    details.

  • On macOS rig now includes a menu bar app that show the default R version,
    lets you choose between R versions and libraries, and lets you start
    RStudio with a specific R version, and/or a recent RStudio project.
    Start the app with open -a Rig.

  • New subcommand rig system setup-user-lib to update the R config to create
    the user package library when R starts up, if it does not exist. The old
    rig system create-lib subcommand is now an alias of this.

  • Better messages. rig has a -v and -vv flag now, for extra debug and
    trace messages.

  • On arm64 macOS, rig add installs arm64 R by default now.
    (This is also true for the x86_64 build of rig.

  • On macOS rig add does not change the default R version any more (#2).

  • rig now supports Linux distros based on Ubuntu Bionic 18.04, Focal 20.04
    and Jammy 22.04. They need to have a proper UBUNTU_CODENAME entry in
    /etc/os-release (#34).

  • rig now sets up automated system requirements installation with pak on Linux
    distributions that support it: Ubuntu 18.04, 20.04 and 22.04 (on distros
    based on these), on both x86_64 and aarch64. (This currently needs
    passwordless sudo or a root account.)

  • All OSes create an Rscript link now that runs the default R
    version (#20).


This package has no dependencies.

Discussion for the rig Package

Ground Rules:

  • This discussion is only about rig and the rig package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or rig, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus