Downloads:

141,440

Downloads of v 3.20.2:

2,108

Last Update:

15 Sep 2022

Package Maintainer(s):

Software Author(s):

  • Google

Tags:

protoc protobuf foss cross-platform

Protocol Buffers

  • 1
  • 2
  • 3

3.20.2 | Updated: 15 Sep 2022

Downloads:

141,440

Downloads of v 3.20.2:

2,108

Software Author(s):

  • Google

  • 1
  • 2
  • 3
Protocol Buffers 3.20.2

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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:

>

Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade protoc -y --source="'INTERNAL REPO 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="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install protoc
  win_chocolatey:
    name: protoc
    version: '3.20.2'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'protoc' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.20.2'
end

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


cChocoPackageInstaller protoc
{
    Name     = "protoc"
    Version  = "3.20.2"
    Source   = "INTERNAL REPO URL"
}

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


package { 'protoc':
  ensure   => '3.20.2',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 15 Sep 2022.

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/v3.20.2/protoc-3.20.2-win32.zip>
  64-bit zip file: <https://github.com//protocolbuffers/protobuf/releases/download/v3.20.2/protoc-3.20.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: 839B3A989CBD3AA9803695155BC475B5901D961557A3B128528240091A900F81
  checksum64: C19C84B003FE9EB84A77D108F072A958EE4BCFEB91FC040A391F16138AA5174C

File 'LICENSE' is obtained from <https://github.com/protocolbuffers/protobuf/blob/master/LICENSE>
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'

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

$packageArgs = @{
  PackageName    = $Env:ChocolateyPackageName
  FileFullPath   = "$toolsPath\protoc-3.20.2-win32.zip"
  FileFullPath64 = "$toolsPath\protoc-3.20.2-win64.zip"
  Destination    = $toolsPath
}
Get-ChocolateyUnzip @packageArgs
Remove-Item $toolsPath\*.zip -ea 0
tools\protoc-3.20.2-win32.zip
md5: A421B9397616A0DC9656C9143983DBED | sha1: D67646F7ECA650AA7BA2C74C91C99F04CD7FB37E | sha256: 839B3A989CBD3AA9803695155BC475B5901D961557A3B128528240091A900F81 | sha512: D57C606854D7BEB8C701F0AAF6C6CAC010D06E8E1D765D9C8EC5C49ADDD611522F3CF864DD85F9DB2CA8E772AEC6134739D60C75BFF75F564E205FE4B529D105
tools\protoc-3.20.2-win64.zip
md5: D2A9D2249A569858919C44C42B26E5EA | sha1: FBC5FD6D212C29DFBF3A8F6FFF2B6224BC328BFC | sha256: C19C84B003FE9EB84A77D108F072A958EE4BCFEB91FC040A391F16138AA5174C | sha512: 5DD6732E439BC39CCB278F88D56DCB0601FC82749648F9868B4DFDE444D507CF8BED5273226DCD364018090C8C894B081C023A1ECA5BEE4FD71F716BBCBA6A4F

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.

Add to Builder Version Downloads Last Updated Status
Protocol Buffers 3.20.1 14974 Friday, April 22, 2022 Approved
Protocol Buffers 3.20.0 1318 Saturday, March 26, 2022 Approved
Protocol Buffers 3.19.4 10226 Friday, January 28, 2022 Approved
Protocol Buffers 3.19.3 807 Tuesday, January 11, 2022 Approved
Protocol Buffers 3.19.2 293 Thursday, January 6, 2022 Approved
Protocol Buffers 3.19.1 2108 Friday, October 29, 2021 Approved
Protocol Buffers 3.19.0 545 Thursday, October 21, 2021 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