Downloads:

14,547

Downloads of v 1.66:

1,291

Last Update:

26 May 2016

Package Maintainer(s):

Software Author(s):

  • Al Danial

Tags:

loc sloc cloc count lines code

Count Lines of Code (CLOC)

This is not the latest version of Count Lines of Code (CLOC) available.

1.66 | Updated: 26 May 2016

Downloads:

14,547

Downloads of v 1.66:

1,291

Software Author(s):

  • Al Danial

Count Lines of Code (CLOC) 1.66

This is not the latest version of Count Lines of Code (CLOC) available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Count Lines of Code (CLOC), run the following command from the command line or from PowerShell:

>

To upgrade Count Lines of Code (CLOC), run the following command from the command line or from PowerShell:

>

To uninstall Count Lines of Code (CLOC), 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 cloc -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 cloc -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 cloc installed
  win_chocolatey:
    name: cloc
    state: present
    version: 1.66
    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 'cloc' do
  action    :install
  version  '1.66'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: cloc,
    Version: 1.66,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller cloc
{
   Name     = 'cloc'
   Ensure   = 'Present'
   Version  = '1.66'
   Source   = 'STEP 3 URL'
}

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


package { 'cloc':
  provider => 'chocolatey',
  ensure   => '1.66',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install cloc version="1.66" 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 was approved by moderator dtgm on 26 May 2016.

Description

Cloc counts blank lines, comment lines, and physical lines of source code in many programming languages. Given two versions of a code base, cloc can compute differences in blank, comment, and source lines. It is written entirely in Perl with no dependencies outside the standard distribution of Perl v5.6 and higher (code from some external modules is embedded within cloc) and so is quite portable.


tools\bins.ps1
<#
  .SYNOPSIS

  Create a .ignore file for a package binary.

  .DESCRIPTION

  Chocolatey automatically creates a "shim" in a special folder, on your
  machine's PATH, for any executables found in the package's installation
  directory. This is helpful when installing ZIP packages or any kind of
  command line tools.

  Chocolatey can be instructed to ignore a particular binary by creating a file
  at the same path with the same name as the binary to ignore, except ending
  with the file extension ".ignore".

  This function creates that file, given the binary's path.

  .PARAMETER Path

  The path of the binary to ignore.

  This parameter also accepts multiple paths or pipeline input.

  .EXAMPLE

  Install-IgnoreBin -Path "foo.exe"

  .EXAMPLE

  Install-IgnoreBin -Path $foo, $bar

  .EXAMPLE

  Get-ChildItem "$content\foo\*.exe" | Install-IgnoreBin

  .LINK

  https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function Install-IgnoreBin {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory = $true, ValueFromPipeline = $true)]
    [ValidateNotNullOrEmpty()]
    [ValidateScript({ Test-Path $_ })]
    [string[]] $Path
  )

  PROCESS {
    foreach($item in $Path) {
      New-Item "$(Resolve-Path $item).ignore" -Type "File" -Force | Out-Null
    }
  }
}

<#
  .SYNOPSIS

  Create a .gui file for a package binary.

  .DESCRIPTION

  Chocolatey automatically creates a "shim" in a special folder, on your
  machine's PATH, for any executables found in the package's installation
  directory. This is helpful when installing ZIP packages or any kind of
  command line tools.

  Chocolatey can be instructed to treat a particular binary as a GUI application,
  meaning it will START the binary in a separate process and not block the
  console, by creating a file at the same path with the same name as the binary,
  except ending with the file extension ".gui".

  This function creates that file, given the binary's path.

  .PARAMETER Path

  The path of the binary to treat as a GUI application.

  This parameter also accepts multiple paths or pipeline input.

  .EXAMPLE

  Install-GuiBin -Path "foo.exe"

  .EXAMPLE

  Install-GuiBin -Path $foo, $bar

  .EXAMPLE

  Get-ChildItem "$content\foo\*.exe" | Install-GuiBin

  .LINK

  https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function Install-GuiBin {
  [CmdletBinding()]
  param(
    [Parameter(Mandatory = $true, ValueFromPipeline = $true)]
    [ValidateNotNullOrEmpty()]
    [ValidateScript({ Test-Path $_ })]
    [string[]] $Path
  )

  PROCESS {
    foreach($item in $Path) {
      New-Item "$(Resolve-Path $item).gui" -Type "File" -Force | Out-Null
    }
  }
}
tools\chocolateyInstall.ps1
$tools = Split-Path $MyInvocation.MyCommand.Definition
$content = Join-Path (Split-Path $tools) 'content'
$bin = Join-Path $content 'cloc-1.66.exe'

. $tools\bins.ps1

New-Item -Type 'Directory' -Path $content -Force | Out-Null

Get-ChocolateyWebFile `
    -PackageName 'cloc' `
    -Url 'https://github.com/AlDanial/cloc/releases/download/v1.66/cloc-1.66.exe' `
    -Checksum '54D6662E59B04BE793DD10FA5E5EDF7747CF0C0CC32F71EB67A3CF8E7A171D81' `
    -ChecksumType 'SHA256' `
    -FileFullPath $bin

Install-IgnoreBin `
    -Path $bin

Install-BinFile `
    -Name 'cloc' `
    -Path $bin
tools\chocolateyUninstall.ps1
$tools = Split-Path $MyInvocation.MyCommand.Definition
$content = Join-Path (Split-Path $tools) 'content'
$bin = Join-Path $content 'cloc-1.66.exe'

Uninstall-BinFile `
    -Name 'cloc' `
    -Path $bin

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
Count Lines of Code (CLOC) 1.80 3908 Tuesday, December 18, 2018 Approved
Count Lines of Code (CLOC) 1.76 3208 Monday, May 14, 2018 Approved
Count Lines of Code (CLOC) 1.72 2244 Thursday, September 7, 2017 Approved
Count Lines of Code (CLOC) 1.70 193 Thursday, September 7, 2017 Approved
Count Lines of Code (CLOC) 1.68 201 Thursday, September 7, 2017 Approved
Count Lines of Code (CLOC) 1.66 1291 Thursday, May 26, 2016 Approved
Count Lines of Code (CLOC) 1.62 798 Thursday, September 11, 2014 Approved
CLOC 1.56 505 Saturday, November 17, 2012 Approved

This package has no dependencies.

Discussion for the Count Lines of Code (CLOC) Package

Ground Rules:

  • This discussion is only about Count Lines of Code (CLOC) and the Count Lines of Code (CLOC) 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 Count Lines of Code (CLOC), 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