Downloads:

848

Downloads of v 0.5.4:

444

Last Update:

20 Apr 2021

Package Maintainer(s):

Software Author(s):

  • Manfred Wallner

Tags:

chocolatey local tool roco

ROCO(latey)

  • 1
  • 2
  • 3

0.5.4 | Updated: 20 Apr 2021

Downloads:

848

Downloads of v 0.5.4:

444

Maintainer(s):

Software Author(s):

  • Manfred Wallner

  • 1
  • 2
  • 3
ROCO(latey) 0.5.4

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install ROCO(latey), run the following command from the command line or from PowerShell:

>

To upgrade ROCO(latey), run the following command from the command line or from PowerShell:

>

To uninstall ROCO(latey), 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 rocolatey -y --source="'INTERNAL REPO URL'" [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 rocolatey -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install rocolatey
  win_chocolatey:
    name: rocolatey
    version: '0.5.4'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'rocolatey' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.5.4'
end

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


cChocoPackageInstaller rocolatey
{
    Name     = "rocolatey"
    Version  = "0.5.4"
    Source   = "INTERNAL REPO URL"
}

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


package { 'rocolatey':
  ensure   => '0.5.4',
  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.

This package was approved by moderator virtualex on 20 Apr 2021.

Description

R(ocket-fast) Chocolatey queries.

  • mimics output of Chocolatey commands (drop-in replacement)
  • doesn't make use of Chocolatey or chocolatey.dll - just looks at the filesystem / does native ODATA calls.
  • can be used to query Chocolatey status while choco.exe is running.
  • it's supposed to be much faster for each command that has a Chocolatey counterpart.

What can roco do for me?

Take a look at the help (roco -h), basically roco allows you to list installed packages, list failed package installs, configured sources and check for updates. In addition to that, there may be some hidden gems that are only available in roco, but not in vanilla Chocolatey.

choco command roco command
choco source list roco source
choco list -lo roco list
choco outdated roco outdated
- roco bad
- ... :wink:

Normally you should not run multiple Chocolatey instances at the same time, however this may be required in certain scenarios. If you wanted to check if updates are available, or simply list all configured sources, roco is there to help you out without worrying of breaking something because you accidentally called choco in parallel.

How much faster is roco.exe compared to choco.exe?

It very much depends on the number of installed packages and configured feeds, generally speaking roco should always be much faster than choco, the difference becomes bigger when dealing with many packages and feeds.


tools\LICENSE.txt
MIT License

Copyright (c) 2021 Manfred Wallner

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\roco.exe
md5: 9CAC86EC0D650CA462D4B95C57115E97 | sha1: D9CA783E3FDAF62335D355295D8BC60C1EEFC1F5 | sha256: 70D23E81D84C3A6C8A20DF51707AF4618CD42187D49C6DB2D0F539B204CCF0F4 | sha512: 89C72829711974161510AB247CC31F3D45623A970EAC1150AE6F5EDCFAAC33FE4F240DCA19C119475186E076389AB4A2F80788CFC35EB09FEA6363726F900724
tools\rocolatey-server.exe
md5: 7812B8FBDCECCD3BF4F2AC0CD22EA3A7 | sha1: 64DF169384C3444352D51CFC8EE97FA8A1B52AC8 | sha256: DF60B2A998F4DE601137030BB4F723315930E1F24E222751C67F3EB43F19D5BF | sha512: B86092B1D6548F5CBB675AA34552073A23BAFE5C57BFBD40FE0FF269771D4AE27FEF0E4868BA8C930877F0932EB1E0964AE5CBFE1CB1D44BBB8E473D6E26A944
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

I am the author of this software.

The checksums of the files included should match the corresponding version on https://github.com/mwallner/rocolatey/releases

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
ROCO(latey) 0.5.3 109 Tuesday, March 23, 2021 Approved
ROCO(latey) 0.5.2 91 Tuesday, February 2, 2021 Approved
ROCO(latey) 0.5.0-beta2 74 Friday, January 8, 2021 Exempted
ROCO(latey) 0.4.0 95 Monday, January 4, 2021 Approved
Discussion for the ROCO(latey) Package

Ground Rules:

  • This discussion is only about ROCO(latey) and the ROCO(latey) 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 ROCO(latey), 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