Downloads:

913,278

Downloads of v 58.0.2996.0:

286

Last Update:

1/28/2017

Package Maintainer(s):

Software Author(s):

  • The Chromium Authors

Tags:

chromium admin google cross-platform foss chrome browser

Chromium snapshots build

This is not the latest version of Chromium snapshots build available.

58.0.2996.0 | Updated: 1/28/2017

Downloads:

913,278

Downloads of v 58.0.2996.0:

286

Maintainer(s):

Software Author(s):

  • The Chromium Authors

Chromium snapshots build 58.0.2996.0

This is not the latest version of Chromium snapshots build available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Chromium snapshots build, run the following command from the command line or from PowerShell:

>

To upgrade Chromium snapshots build, run the following command from the command line or from PowerShell:

>

To uninstall Chromium snapshots build, run the following command from the command line or from PowerShell:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade chromium -y --source="'STEP 3 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 chromium -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure chromium installed
  win_chocolatey:
    name: chromium
    state: present
    version: 58.0.2996.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'chromium' do
  action    :install
  version  '58.0.2996.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: chromium,
    Version: 58.0.2996.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller chromium
{
   Name     = 'chromium'
   Ensure   = 'Present'
   Version  = '58.0.2996.0'
   Source   = 'STEP 3 URL'
}

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


package { 'chromium':
  provider => 'chocolatey',
  ensure   => '58.0.2996.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install chromium version="58.0.2996.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 1/28/2017.

Description

This package installs the Chromium snapshots builds by default to the '%programfiles(x86)%' instead of %localappdata%\Chromium.
If you have installed this package in the past to the %localappdata%\Chromium location it will continue to be installed in this location.
These builds can be unstable. MD5 checking is done on the file before install.


tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$version = '58.0.2996.0'

$chromium_string = "\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Chromium"
$hive = "hkcu"
$Chromium = $hive + ":" + $chromium_string

if (Test-Path $Chromium) {
  $silentArgs = '--do-not-launch-chrome'
} else {
  $silentArgs = '--system-level --do-not-launch-chrome'
}

$packageArgs = @{
  packageName   = 'chromium'
  fileType      = 'exe'
  url           = 'https://storage.googleapis.com/chromium-browser-snapshots/Win/446919/mini_installer.exe'
  url64bit      = 'https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/446919/mini_installer.exe'
  silentArgs    = $silentArgs
  validExitCodes= @(0)
  softwareName  = 'Chromium'
  checksum      = '8fdf08fa07a98c0c8231d7c27b9e1d28'
  checksumType  = 'md5'
  checksum64    = 'cd1e85bffb64e302cc9c7bd79016f600'
  checksumType64= 'md5'
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyUninstall.ps1
	$registry = Get-UninstallRegistryKey -SoftwareName $packageName
	$file = $registry.UninstallString
  $Arg_chk = ($file -match "--system-level")
	$chromiumArgs = @{$true = "--uninstall --system-level"; $false = "--uninstall"}[ $Arg_chk ]
	$silentArgs = @{$true = '--uninstall --system-level --force-uninstall'; $false = '--uninstall --force-uninstall'}[ $Arg_chk ]
	$myfile = $file -replace( $chromiumArgs )
	# All arguments for the Uninstallation of this package
	$packageArgs = @{
	PackageName = 'Chromium'
	FileType = 'exe'
	SilentArgs = $silentArgs
	validExitCodes =  @(0,19,21)
	File = $myfile
	}
	# Now to Uninstall the Package
	Uninstall-ChocolateyPackage @packageArgs
	# This at the moment does not remove the libs\Chromium folder

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.

Version Downloads Last Updated Status
Chromium Snapshots 80.0.3966.0-snapshots 16 Tuesday, November 12, 2019 Approved
Chromium Snapshots 80.0.3965.0-snapshots 54 Monday, November 11, 2019 Approved
Chromium Snapshots 80.0.3962.0-snapshots 126 Wednesday, November 6, 2019 Approved
Chromium Snapshots 80.0.3961.0-snapshots 10 Wednesday, November 6, 2019 Approved
Chromium Snapshots 80.0.3956.0-snapshots 185 Thursday, October 31, 2019 Approved
Chromium Snapshots 80.0.3955.0-snapshots 57 Wednesday, October 30, 2019 Approved
Chromium Snapshots 80.0.3954.0-snapshots 38 Wednesday, October 30, 2019 Approved
Chromium Snapshots 80.0.3953.0-snapshots 91 Tuesday, October 29, 2019 Approved
Chromium Snapshots 80.0.3952.0-snapshots 69 Saturday, October 26, 2019 Approved
Chromium Snapshots 80.0.3950.0-snapshots 126 Thursday, October 24, 2019 Approved

This package has no dependencies.

Discussion for the Chromium snapshots build Package

Ground Rules:

  • This discussion is only about Chromium snapshots build and the Chromium snapshots build 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 Chromium snapshots build, 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