Downloads:

62,286

Downloads of v 4.0.0-rc-2:

260

Last Update:

22 Jul 2020

Package Maintainer(s):

Software Author(s):

  • Google

Tags:

protoc protobuf foss cross-platform

Protocol Buffers

This is a prerelease version of Protocol Buffers.

4.0.0-rc-2 | Updated: 22 Jul 2020

Downloads:

62,286

Downloads of v 4.0.0-rc-2:

260

Software Author(s):

  • Google

Protocol Buffers 4.0.0-rc-2

This is a prerelease version of Protocol Buffers.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Protocol Buffers, run the following command from the command line or from PowerShell:

>

To upgrade Protocol Buffers, run the following command from the command line or from PowerShell:

>

To uninstall Protocol Buffers, 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 protoc -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 protoc -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 protoc installed
  win_chocolatey:
    name: protoc
    state: present
    version: 4.0.0-rc-2
    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 'protoc' do
  action    :install
  version  '4.0.0-rc-2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: protoc,
    Version: 4.0.0-rc-2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller protoc
{
   Name     = 'protoc'
   Ensure   = 'Present'
   Version  = '4.0.0-rc-2'
   Source   = 'STEP 3 URL'
}

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


package { 'protoc':
  provider => 'chocolatey',
  ensure   => '4.0.0-rc-2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install protoc version="4.0.0-rc-2" 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 22 Jul 2020.

Description

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data.

This is chocolatey package for the prebuilt Protocol Buffers Compiler.

Features

  • Flexible, efficient, automated mechanism for serializing structured data – think XML, but smaller, faster, and simpler.
  • Define how you want your data to be structured once, then use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages.
  • Update your data structure without breaking deployed programs that are compiled against the "old" format.

legal\LICENSE.txt
Copyright 2008 Google Inc.  All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

    * Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
    * Neither the name of Google Inc. nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Code generated by the Protocol Buffer compiler is owned by the owner
of the input file used when generating it.  This code is not
standalone and requires a support library to be linked with it.  This
support library is itself covered by the above license.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The zip file have been downloaded from the github release page on <https://github.com/protocolbuffers/protobuf/releases>
and can be verified like this:

1. Download the following:
  32-bit zip file: <https://github.com//protocolbuffers/protobuf/releases/download/v4.0.0-rc2/protoc-4.0.0-rc-2-win32.zip>
  64-bit zip file: <https://github.com//protocolbuffers/protobuf/releases/download/v4.0.0-rc2/protoc-4.0.0-rc-2-win64.zip>
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum32: 9119B145B83E199F5A34417CB21112A12BA084435776F4FA827AD7746DEFDA34
  checksum64: A3BDC2BB72F074239E28BFCDFA2806E725B6E833AA03B2507E0009C19D1A0DE1

File 'LICENSE' is obtained from <https://github.com/protocolbuffers/protobuf/blob/master/LICENSE>
tools\chocolateyBeforeModify.ps1
Write-Host "Removing protoc shim before upgrading/uninstalling..."

Uninstall-BinFile "protoc" -path "$(Split-Path -parent $MyInvocation.MyCommand.Definition)\bin\protoc.exe"
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

$packageArgs = @{
  PackageName    = $Env:ChocolateyPackageName
  FileFullPath   = "$toolsPath\protoc-4.0.0-rc-2-win32.zip"
  FileFullPath64 = "$toolsPath\protoc-4.0.0-rc-2-win64.zip"
  Destination    = $toolsPath
}
Get-ChocolateyUnzip @packageArgs
Remove-Item $toolsPath\*.zip -ea 0

Install-BinFile 'protoc' "$toolsPath\bin\protoc.exe"
tools\protoc-4.0.0-rc-2-win32.zip
md5: 20AF7A82C925BB40516BE65B83828E62 | sha1: 834D38A8520C090F47CDE0DFD5BD3C15FC18246C | sha256: 9119B145B83E199F5A34417CB21112A12BA084435776F4FA827AD7746DEFDA34 | sha512: 7D7AF697169B25D1C6D18988D97ECE3A9BA1D5F172EC517E3B2AC532190E6A0458DB4A5EA3FA55B43832EE093688306FAFA759E6993EF0997748D1B5B85E63DC
tools\protoc-4.0.0-rc-2-win64.zip
md5: 46D7FCA83D71061ECF79BF4292BAB73D | sha1: 685816B774F594296F5DD132C117B12D33AD9216 | sha256: A3BDC2BB72F074239E28BFCDFA2806E725B6E833AA03B2507E0009C19D1A0DE1 | sha512: A9DA01277419BC30BD7C4F655CF955A00DFAC4C7BCC1432A5F2ED22E84E7E038B9A53EBB8AB19AF7471607A37216C5BA935DA47219096325C0921A266F510234

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
Protocol Buffers 4.0.0-rc-2 260 Wednesday, July 22, 2020 Approved
Protocol Buffers 4.0.0-rc-1 32 Wednesday, July 15, 2020 Approved
Protocol Buffers 3.12.2 716 Wednesday, May 27, 2020 Approved
Protocol Buffers 3.12.1 623 Thursday, May 21, 2020 Approved
Protocol Buffers 3.12.0 983 Saturday, May 16, 2020 Approved
Protocol Buffers 3.12.0-rc-2 34 Wednesday, May 13, 2020 Approved
Protocol Buffers 3.12.0-rc-1 40 Monday, May 4, 2020 Approved
Protocol Buffers 3.11.4 7597 Saturday, February 15, 2020 Approved
Protocol Buffers 3.11.3 305 Monday, February 3, 2020 Approved
Discussion for the Protocol Buffers Package

Ground Rules:

  • This discussion is only about Protocol Buffers and the Protocol Buffers 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 Protocol Buffers, 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