Downloads:

252,076

Downloads of v 4.8.8:

1,794

Last Update:

11 Jun 2017

Package Maintainer(s):

Software Author(s):

  • Paket team

Tags:

nuget bundler F#

Paket.PowerShell

4.8.8 | Updated: 11 Jun 2017

Downloads:

252,076

Downloads of v 4.8.8:

1,794

Maintainer(s):

Software Author(s):

  • Paket team

Tags:

nuget bundler F#

Paket.PowerShell 4.8.8

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall Paket.PowerShell, 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 paket.powershell -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 paket.powershell -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 paket.powershell installed
  win_chocolatey:
    name: paket.powershell
    state: present
    version: 4.8.8
    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 'paket.powershell' do
  action    :install
  version  '4.8.8'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: paket.powershell,
    Version: 4.8.8,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller paket.powershell
{
   Name     = 'paket.powershell'
   Ensure   = 'Present'
   Version  = '4.8.8'
   Source   = 'STEP 3 URL'
}

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


package { 'paket.powershell':
  provider => 'chocolatey',
  ensure   => '4.8.8',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install paket.powershell version="4.8.8" 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 09 Jul 2020.

Description

A dependency manager for .NET with support for NuGet packages and git repositories.


tools\chocolateyInstall.ps1
$tools = "$env:chocolateyPackageFolder\tools"
. "$tools\Install-PSModulePath.ps1"
Install-PSModulePath -pathToInstall $tools -pathType ([System.EnvironmentVariableTarget]::Machine)
tools\init.ps1
param($installPath, $toolsPath, $package)
Import-Module (Join-Path $toolsPath 'Paket.PowerShell\Paket.PowerShell.psd1') -DisableNameChecking
tools\Install-PSModulePath.ps1
# Copyright 2011 - Present RealDimensions Software, LLC & original authors/contributors from https://github.com/chocolatey/chocolatey
# 
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# 
#     http://www.apache.org/licenses/LICENSE-2.0
# 
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

function Install-PSModulePath {
param(
  [string] $pathToInstall,
  [System.EnvironmentVariableTarget] $pathType = [System.EnvironmentVariableTarget]::User
)
  Write-Debug "Running 'Install-PSModulePath' with pathToInstall:`'$pathToInstall`'";
  $originalPathToInstall = $pathToInstall

  #get the PSModulePath variable
  Update-SessionEnvironment
  $envPath = $env:PSModulePath
  if (!$envPath.ToLower().Contains($pathToInstall.ToLower()))
  {
    Write-Host "PSModulePath environment variable does not have $pathToInstall in it. Adding..."
    $actualPath = Get-EnvironmentVariable -Name 'PSModulePath' -Scope $pathType

    $statementTerminator = ";"
    #does the path end in ';'?
    $hasStatementTerminator = $actualPath -ne $null -and $actualPath.EndsWith($statementTerminator)
    # if the last digit is not ;, then we are adding it
    If (!$hasStatementTerminator -and $actualPath -ne $null) {$pathToInstall = $statementTerminator + $pathToInstall}
    if (!$pathToInstall.EndsWith($statementTerminator)) {$pathToInstall = $pathToInstall + $statementTerminator}
    $actualPath = $actualPath + $pathToInstall

    if ($pathType -eq [System.EnvironmentVariableTarget]::Machine) {
      if (Test-ProcessAdminRights) {
        Set-EnvironmentVariable -Name 'PSModulePath' -Value $actualPath -Scope $pathType
      } else {
        $psArgs = "Install-PSModulePath -pathToInstall `'$originalPathToInstall`' -pathType `'$pathType`'"
        Start-ChocolateyProcessAsAdmin "$psArgs"
      }
    } else {
      Set-EnvironmentVariable -Name 'PSModulePath' -Value $actualPath -Scope $pathType
    }

    #add it to the local path as well so users will be off and running
    $envPSPath = $env:PSModulePath
    $env:PSModulePath = $envPSPath + $statementTerminator + $pathToInstall
  }
}

# [System.Text.RegularExpressions.Regex]::Match($Path,[System.Text.RegularExpressions.Regex]::Escape('locationtoMatch') + '(?>;)?', '', [System.Text.RegularExpressions.RegexOptions]::IgnoreCase)
tools\Paket.PowerShell\ArgumentTabCompletion.ps1

# http://stackoverflow.com/questions/30923696/add-custom-argument-completer-for-cmdlet

# https://github.com/mariuszwojcik/RabbitMQTools/blob/master/TabExpansions.ps1
function createCompletionResult([string]$text, [string]$value, [string]$tooltip) {
    if ([string]::IsNullOrEmpty($value)) { return }
    if ([string]::IsNullOrEmpty($text)) { $text = $value }
    if ([string]::IsNullOrEmpty($tooltip)) { $tooltip = $value }
    $completionText = @{$true="'$value'"; $false=$value  }[$value -match "\W"]
    $completionText = $completionText -replace '\[', '``[' -replace '\]', '``]'
    New-Object System.Management.Automation.CompletionResult $completionText, $text, 'ParameterValue', $tooltip | write
}

$findPackages = {
    param($commandName, $parameterName, $wordToComplete, $commandAst, $fakeBoundParameter)
    Paket-FindPackages -SearchText $wordToComplete -Max 100 | % {
        createCompletionResult $_ $_ $_ | write
    }
}

$findPackageVersions = {
    param($commandName, $parameterName, $wordToComplete, $commandAst, $fakeBoundParameter)
    if (-not $fakeBoundParameter.NuGet){ return }
    Paket-FindPackageVersions -Name $fakeBoundParameter.NuGet -Max 100 | % {
        createCompletionResult $_ $_ $_ | write
    }
}

$showInstalledPackages = {
    param($commandName, $parameterName, $wordToComplete, $commandAst, $fakeBoundParameter)
    Paket-ShowInstalledPackages | % {
		$name = $_.Name
        createCompletionResult $name $name $name | write
    }
}

# create and add $global:options to the list of completers
# http://www.powertheshell.com/dynamicargumentcompletion/
if (-not $global:options) { $global:options = @{CustomArgumentCompleters = @{};NativeArgumentCompleters = @{}}}

$global:options['CustomArgumentCompleters']['Paket-Add:NuGet'] = $findPackages
$global:options['CustomArgumentCompleters']['Paket-Add:Version'] = $findPackageVersions
$global:options['CustomArgumentCompleters']['Paket-Update:NuGet'] = $showInstalledPackages
$global:options['CustomArgumentCompleters']['Paket-Update:Version'] = $findPackageVersions
$global:options['CustomArgumentCompleters']['Paket-Remove:NuGet'] = $showInstalledPackages
$global:options['CustomArgumentCompleters']['Paket-FindPackageVersions:Name'] = $findPackages
$global:options['CustomArgumentCompleters']['Paket-FindRefs:NuGet'] = $showInstalledPackages

$function:tabexpansion2 = $function:tabexpansion2 -replace 'End\r\n{','End { if ($null -ne $options) { $options += $global:options} else {$options = $global:options}'
tools\Paket.PowerShell\Paket.PowerShell.dll
md5: 4E966DAA86137D819930ECB074EB63E1 | sha1: 981068559E0EFA653826B00FE9EBFBC89201BCA3 | sha256: 0D7F3C252DD451DCA3F0BA4AD2B77E659631417204E5EE9BEBA9C49330ABEA10 | sha512: 44FC2EEDF138BDF9F082D620D0518AE6A73A4C105DBEA70BDAF577799AB31DA26648B240F0EC45C208757335880D953A4D45981A1A06C918BDCDC646F0603486
tools\Paket.PowerShell\Paket.PowerShell.psd1
@{
GUID = 'e7bdf748-93e9-4e24-95a2-ace98df3d687'
Author = 'Paket'
Copyright = '(c) 2015 Paket. All rights reserved.'
PowerShellVersion = '3.0'
CLRVersion = '4.0'
RootModule = 'Paket.PowerShell.dll'
HelpInfoUri = 'http://fsprojects.github.io/Paket/'
ScriptsToProcess = 'ArgumentTabCompletion.ps1'
# the build will append these lines
# ModuleVersion = '1.0.0'
# }
ModuleVersion = '4.8.8'
}

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.

Version Downloads Last Updated Status
Paket.PowerShell 5.0.0-alpha007 425 Friday, April 28, 2017 Approved
Paket.PowerShell 5.0.0-alpha006 252 Friday, April 28, 2017 Approved
Paket.PowerShell 5.0.0-alpha005 258 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha004 278 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha003 239 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha002 265 Thursday, April 27, 2017 Approved
Paket.PowerShell 5.0.0-alpha001 258 Thursday, April 27, 2017 Approved
Paket.PowerShell 4.8.7 255 Friday, June 2, 2017 Approved
Paket.PowerShell 4.8.6 268 Tuesday, May 23, 2017 Approved

paket adds too many targets and props (https://github.com/fsprojects/Paket/pull/2388)


This package has no dependencies.

Discussion for the Paket.PowerShell Package

Ground Rules:

  • This discussion is only about Paket.PowerShell and the Paket.PowerShell 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 Paket.PowerShell, 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