Downloads:

2,931

Downloads of v 1.9.4:

303

Last Update:

11/15/2016

Package Maintainer(s):

Software Author(s):

  • Henry++

Tags:

chrlauncher chromium chrome updater portable

chrlauncher (portable)

This is not the latest version of chrlauncher (portable) available.

1.9.4 | Updated: 11/15/2016

Downloads:

2,931

Downloads of v 1.9.4:

303

Maintainer(s):

Software Author(s):

  • Henry++

chrlauncher (portable) 1.9.4

This is not the latest version of chrlauncher (portable) available.

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: 1.9.4
    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  '1.9.4'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: chrlauncher.portable,
    Version: 1.9.4,
    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  = '1.9.4'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install chrlauncher.portable version="1.9.4" 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.

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

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 by moderator flcdrg on 11/24/2016.

Description

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

Package Parameters

The following package parameters can be set:

  • /Flash - Include the Adobe Flash Player Pepper Plugin API (PPAPI) DLL. see here

  • /Default - Make chrlauncher the default "browser". This option requires installing with admin rights.

These parameters can be passed to the installer with the use of -params.
For example:
-params '"/Default"'.


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

$PackageName = "chrlauncher.portable"
$version = '1.9.4'
$Url = "https://github.com/henrypp/chrlauncher/releases/download/v.$version/chrlauncher-$version-without-ppapi-bin.zip" 
$checkSum = '2AE995F2CC1E0ACE9B549C09CD78114BBBB2C087ABF0227BE842055843A4299D'

$UserArguments = @{}
 
# Parse the packageParameters using good old regular expression
if ($env:chocolateyPackageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    $option_name = 'option'
    $value_name = 'value'
 
    if ($env:chocolateyPackageParameters -match $match_pattern ){
        $results = $env:chocolateyPackageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
        $UserArguments.Add(
            $_.Groups[$option_name].Value.Trim(),
            $_.Groups[$value_name].Value.Trim())
    }
    }
    else
    {
        Throw 'Package Parameters were found but were invalid (REGEX Failure)'
    }
  
} else {
    Write-Debug 'No Package Parameters Passed in'
}

if ($UserArguments.ContainsKey('Flash')) {
   Write-Host 'You want the Flash Pepper Plugin API (PPAPI) included.'
   $URL = $Url.replace('-without-ppapi','')
   $checkSum = 'F901A439F60F49FEB4DF8D43D405B0C8C214C7FA7E959C2BF33FE26B09FFE5F4'
}

$PackageDir = Split-path (Split-path $MyInvocation.MyCommand.Definition)

$InstallArgs = @{
   PackageName = $PackageName
   Url = $URL 
   UnzipLocation = (Join-path $PackageDir ($PackageName.split('.')[0] + $version))
   checkSum = $checkSum
   checkSumType = 'sha256'
}
Install-ChocolateyZipPackage @InstallArgs

$BitLevel = Get-ProcessorBits

if ($UserArguments.ContainsKey('Default')) {
   Write-Host 'You want chrlauncher as your default browser.'
   $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
}

$target   = Join-Path $InstallArgs.UnzipLocation "$BitLevel\chrlauncher.exe"
$shortcut = Join-Path ([System.Environment]::GetFolderPath('Desktop')) 'Chromium Launcher.lnk'

Install-ChocolateyShortcut -ShortcutFilePath $shortcut -TargetPath $target

tools\chocolateyUninstall.ps1
$PackageName = "chrlauncher.portable"
$version = '1.9.4'
$PackageDir = Split-path (Split-path $MyInvocation.MyCommand.Definition)

Remove-Item (Join-path $PackageDir ($PackageName.split('.')[0] + $version)) -Recurse -Force

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


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 60 Thursday, February 28, 2019 Approved
chrlauncher (portable) 2.5.4 128 Friday, December 21, 2018 Approved
chrlauncher (portable) 2.5 94 Friday, November 16, 2018 Approved
chrlauncher (portable) 2.4.3 409 Tuesday, March 13, 2018 Approved
chrlauncher (portable) 2.4.1 429 Saturday, August 5, 2017 Approved
chrlauncher (portable) 2.3 405 Tuesday, February 14, 2017 Approved
chrlauncher (portable) 2.2.0.20170208 240 Wednesday, February 8, 2017 Approved
chrlauncher (portable) 2.2 256 Monday, February 6, 2017 Approved
chrlauncher (portable) 1.9.4 303 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