Downloads:

3,027

Downloads of v 2.5.6:

357

Last Update:

3/16/2019

Package Maintainer(s):

Software Author(s):

  • Henry++

Tags:

chrlauncher chromium chrome updater portable embedded

chrlauncher (portable)

2.5.6 | Updated: 3/16/2019

Downloads:

3,027

Downloads of v 2.5.6:

357

Maintainer(s):

Software Author(s):

  • Henry++

chrlauncher (portable) 2.5.6

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install chrlauncher (portable), run the following command from the command line or from PowerShell:

>

To upgrade chrlauncher (portable), run the following command from the command line or from PowerShell:

>

To uninstall chrlauncher (portable), 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 chrlauncher.portable -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 chrlauncher.portable -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 chrlauncher.portable installed
  win_chocolatey:
    name: chrlauncher.portable
    state: present
    version: 2.5.6
    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 'chrlauncher.portable' do
  action    :install
  version  '2.5.6'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: chrlauncher.portable,
    Version: 2.5.6,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller chrlauncher.portable
{
   Name     = 'chrlauncher.portable'
   Ensure   = 'Present'
   Version  = '2.5.6'
   Source   = 'STEP 3 URL'
}

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


package { 'chrlauncher.portable':
  provider => 'chocolatey',
  ensure   => '2.5.6',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install chrlauncher.portable version="2.5.6" 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 is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 11/6/2019.

Description

A small and very fast portable launcher and updater for Chromium.

This package:

  • installs chrlauncher, not Chromium.
  • will set chrlauncher to download/install/update Chromium without the need for admin rights.
  • by default, sets the install location for Chromium to be the per-user, %APPDATA% directory. Use the /Shared package parameter (below) to make the Chromium install location be in the chrlauncher directory and have Chromium (and all its settings) shared among all users.

Note

Other (system-wide) chrlauncher settings can be modified in the chrlauncher.ini file located in the same directory as the target of the Chromium Launcher desktop shortcut. Some options include:

  • Auto download updates
  • Show a chrlauncher window when updating (default is a tray icon only)
  • Type of Chromium build
  • Update check period

Package Parameters

The following package parameters can be set:

(Adjust the chrlauncher.ini file to manually change the build after installation)

These parameters can be passed to the installer with the use of -params.
For example:
choco install chrlauncher.portable -params '"/Default /KeepSettings"'
choco install chrlauncher.portable -params '"/Type:stable-codecs-sync"'


tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'  # stop on all errors

$ToolsDir   = Join-Path $env:ChocolateyPackageFolder 'tools'
$BitLevel = Get-ProcessorBits

# Capture the newest, previous version's settings
$INIs = Get-ChildItem $env:ChocolateyPackageFolder -Filter '*.ini' -Recurse | 
               Where-Object {$_.Directory -match "\\$BitLevel\\"}
if ($INIs) {
   $NewestVersion = $INIs | ForEach-Object {
                     [version]($_.directory.tostring().trim("$BitLevel\") -replace '.*?([0-9]\.[0-9.]+).*','$1')} | 
                     Sort-Object | Select-Object -Last 1
   $oldINI = Get-Content -Path ($INIs | 
                                 Where-Object {$_.fullname -match $NewestVersion.tostring()} |
                                 Select-Object -ExpandProperty fullname
                               )
}

# Remove previous versions
$Previous = Get-ChildItem $env:ChocolateyPackageFolder | 
               Where-Object{($_.name -match '(chrlauncher)|(v[0-9.]+)') -and $_.PSIsContainer }
if ($Previous) {
   $Previous | ForEach-Object { Remove-Item $_.FullName -Recurse -Force }
}

$InstallArgs = @{
   packageName  = $env:ChocolateyPackageName
   FileFullPath = (Get-ChildItem $ToolsDir -Filter "*.zip").FullName
   Destination  = (Join-path $env:ChocolateyPackageFolder  "v$env:ChocolateyPackageVersion")
}

Get-ChocolateyUnzip @InstallArgs

$target   = (Get-ChildItem $InstallArgs.Destination -filter "*.exe" -Recurse |
               Where-Object {$_.Directory -match "$BitLevel`$"}).FullName
$shortcut = Join-Path ([System.Environment]::GetFolderPath('Desktop')) 'Chromium Launcher.lnk'

Install-ChocolateyShortcut -ShortcutFilePath $shortcut -TargetPath $target

# Capturing Package Parameters.
$UserArguments = Get-PackageParameters

if ($UserArguments['Default']) {
   $msgtext = 'You want chrlauncher as the system default browser.'
   Write-Host $msgtext -ForegroundColor Cyan
   $Bat = Join-Path $InstallArgs.unzipLocation "$BitLevel\SetDefaultBrowser.bat"
   $NoPauseBat = Join-Path (Split-Path $Bat) 'NoPauseSetDefaultBrowser.bat'
   (Get-Content $Bat) -ne 'pause' | Out-File $NoPauseBat -Encoding ascii -Force
   & $NoPauseBat
}

if ($UserArguments['KeepSettings']) {
   $msgtext = 'You want to keep previous installation settings.'
   Write-Host $msgtext -ForegroundColor Cyan
   if ($oldINI) {
      $INIfile = Join-Path (Split-Path $target) 'chrlauncher.ini'
      Rename-Item $INIfile "chrlauncher.ini.orig" -Force
      $oldINI | Out-File $INIfile -Force
      $msgtext = 'Default settings for new version backed up and older version settings restored.'
      Write-Host $msgtext -ForegroundColor Cyan
   } else {
      $msgtext = 'No older settings were found.  Using default settings.'
      Write-Host $msgtext -ForegroundColor Cyan
   }
}

if ($UserArguments['Shared']) {
   $msgtext = 'You want chrlauncher to install/update/launch a single instance of Chromium to be shared (including settings, bookmarks, etc.) among all users.'
   Write-Host $msgtext -ForegroundColor Cyan
   $Acl = get-acl $InstallArgs.UnzipLocation
   $InheritanceFlag = [System.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [System.Security.AccessControl.InheritanceFlags]::ObjectInherit
   $PropagationFlag = [System.Security.AccessControl.PropagationFlags]::InheritOnly
   $rule = New-Object  system.security.accesscontrol.filesystemaccessrule('BUILTIN\Users','Modify',$InheritanceFlag,$PropagationFlag,'Allow')
   $Acl.setaccessrule($rule)
   set-acl $InstallArgs.UnzipLocation $Acl
} else {
   $msgtext = 'chrlauncher will install/update/launch Chromium independently for each user.'
   Write-Host $msgtext -ForegroundColor Cyan
   $INIfile = Join-Path (Split-Path $target) 'chrlauncher.ini'
   (Get-Content $INIfile) -replace "^(ChromiumDirectory=).*$",'$1%LOCALAPPDATA%\Chromium\bin' | Set-Content $INIfile
}

if ($UserArguments['Type']) {
   $msgtext = 'You want to use a Chromium build other than the unofficial development builds with codecs.'
   Write-Host $msgtext -ForegroundColor Cyan
   $NotValid = $false
   switch ($UserArguments['Type']) {
      'dev-official'         { $ValidType = 'dev-official'; break }
      'stable-codecs-sync'   { $ValidType = 'stable-codecs-sync'; break }
      'dev-codecs-nosync'    { $ValidType = 'dev-codecs-nosync'; break }
      'stable-codecs-nosync' { $ValidType = 'stable-codecs-nosync'; break }
      'ungoogled-chromium'   { $ValidType = 'ungoogled-chromium'; break }
      default                { $NotValid = $true; $ValidType = 'dev-codecs-sync' }
   }
   if ($NotValid) {
      $msgtext = "The value '" + $UserArguments['Type'] + "' is not a Chromium build that chrlauncher recognizes." +
                  "`nFalling back to use the default, unofficial development builds with codecs."
      Write-Warning $msgtext
   } else {
      $INIfile = Join-Path (Split-Path $target) 'chrlauncher.ini'
      (Get-Content $INIfile) -replace "^(ChromiumType=).*$","`$1$ValidType" | Set-Content $INIfile
      $msgtext = "chrlauncher will install/update/launch the '$ValidType' Chromium build."
      Write-Host $msgtext -ForegroundColor Cyan
   }
}

tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'  # stop on all errors

# If ChrLauncher was made the default browser, turn that off
if (Test-Path 'HKLM:\Software\Clients\StartMenuInternet\chrlauncher') {
$version = (get-childitem -filter "chrlauncher*" | 
               Where-Object {$_.psiscontainer} | 
               ForEach-Object {[version]($_.name -replace 'chrlauncher','')} |
               Sort-Object)[-1]
$InstallDir = join-path $env:ChocolateyPackageFolder "chrlauncher$($version.tostring())"
$BitLevel = Get-ProcessorBits
   Write-Debug 'Removing registry keys that set chrlauncher as the default browser.'
   $Regfile = Join-Path $InstallDir "$BitLevel\RegistryCleaner.reg"
   regedit /s $Regfile
}

$shortcut = Join-Path ([System.Environment]::GetFolderPath('Desktop')) 'Chromium Launcher.lnk'
 
if ([System.IO.File]::Exists($shortcut)) {
    Write-Debug 'Found the desktop shortcut. Deleting it...'
    [System.IO.File]::Delete($shortcut)
}

tools\chrlauncher-2.5.6-bin.zip
md5: D55CA14FD9903A7E91CA1B0ABC0B2A9D | sha1: D7E7FB970B95719785319DF81A30C9BC696825E0 | sha256: 955B6D8422A0D752C97BADF02C9925195D95D55804516012E2A89AD3005C3A8B | sha512: 468CDB8085DAB733C2D7A8EFB7DF8AA92FF6588150D7EE4A466E65CB1BBB6ED9928E050A1B7A357DDF33E8BCF0E59407FB59237A0F47D84078B5C4FDDF6060F9
tools\LICENSE.txt
Source:  https://github.com/henrypp/chrlauncher/blob/master/LICENSE
-------------------------------------

Copyright (c) 2015-2017, Henry++.

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\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Direct download: 
Version  : 2.5.6
URL      : https://github.com/henrypp/chrlauncher/releases/download/v.2.5.6/chrlauncher-2.5.6-bin.zip
Checksum : 955B6D8422A0D752C97BADF02C9925195D95D55804516012E2A89AD3005C3A8B

An independent Checksum is in this file:
https://github.com/henrypp/chrlauncher/releases/download/v.2.5.6/chrlauncher-2.5.6.sha256

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
chrlauncher (portable) 2.5.5 65 Thursday, February 28, 2019 Approved
chrlauncher (portable) 2.5.4 132 Friday, December 21, 2018 Approved
chrlauncher (portable) 2.5 97 Friday, November 16, 2018 Approved
chrlauncher (portable) 2.4.3 411 Tuesday, March 13, 2018 Approved
chrlauncher (portable) 2.4.1 434 Saturday, August 5, 2017 Approved
chrlauncher (portable) 2.3 411 Tuesday, February 14, 2017 Approved
chrlauncher (portable) 2.2.0.20170208 247 Wednesday, February 8, 2017 Approved
chrlauncher (portable) 2.2 259 Monday, February 6, 2017 Approved
chrlauncher (portable) 1.9.4 306 Tuesday, November 15, 2016 Approved

This package has no dependencies.

Discussion for the chrlauncher (portable) Package

Ground Rules:

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