Package Details: google-cloud-sdk 267.0.0-1

Git Clone URL: (read-only)
Package Base: google-cloud-sdk
Description: A set of command-line tools for the Google Cloud Platform. Includes gcloud (with beta and alpha commands), gsutil, and bq.
Upstream URL:
Keywords: cloud gcloud gcp google sdk
Licenses: Apache
Submitter: barnybug
Maintainer: sudoforge (sudoforge-bot)
Last Packager: sudoforge
Votes: 127
Popularity: 2.061573
First Submitted: 2014-06-03 08:10
Last Updated: 2019-10-15 21:20

Dependencies (2)

Required by (6)

Sources (2)

Pinned Comments

sudoforge commented on 2018-09-10 15:11

To report issues or request features, please use:

sudoforge commented on 2018-08-21 22:09


Commit e01da1e449882ad8e4fe590b01cd09624b58143a removes the appengine components from this package. These components, along with all of the others, will be made available as independent packages in the future.

If you need any of the additional components for your day-to-day workflow, set "disable_updater": false in /opt/google-cloud-sdk/lib/googlecloudsdk/core/config.json and manage components using gcloud components <command>.

Be sure to install any dependencies for the additional components that you may need.

Latest Comments

« First ‹ Previous ... 10 11 12 13 14 15

giniu commented on 2014-06-12 06:46

Hi, now it looks little better, but still some comments:

- you are using unquoted $pkgdir and $srcdir - if someone builds in dir with spaces, things can go wrong. Use "$pkgdir" and "$srcdir" instead.
- by using $pkgdir/opt/google-cloud-sdk/ you are using "python" as interpreter - this script does nothing more than selecting python and running it with correct path, that's why in my example there was python2 instead of If you want to use you should patch it or set environment variables to select python2 instead of python
- not everywhere /usr/bin/env python is used, sometimes it is /usr/bin/python - you need to change those as well
- not all python scripts have .py extension, you need to look for /usr/bin/python and /usr/bin/env python inside them as well
- You have "--path-update true --bash-completion true" while those could be false, then this fake bashrc file will not be created
- You don't have to "mkdir -p $pkgdir/etc/profile.d/" if you use -D in install command, it will create directories

Keep up good work, I will review this package again after more changes. As as I said, try to run:

namcap (resulting file)

it will give you a lot of useful information.

numkem commented on 2014-06-11 14:04

I'm good with that. Need to use it for some project I'm looking into. Still fighting with zsh/bash completions and paths but I'm making progress.


barnybug commented on 2014-06-11 13:46

Hey, I could hand the package over to one of you, this was just a first attempt, and sounds like it'd be in better hands..

numkem commented on 2014-06-11 13:35

I believe I've fixed most issues:

giniu commented on 2014-06-11 13:01

Hello, I plan to move this package to community as last optional dependency of python-pandas, but this needs some clean-up and testing before I can make the move.

I have some comments:
- you install SDK so number should match SDK version number, not gcutil version number (the SDK is numbered 0.9.26).
- you depend on python2 but use python everywhere, interpreter needs to be changed in libraries and correct environment variable needs to be set
- you modify .bashrc in home directory of someone who builds this package, not installs it - correct way is to place scripts in /etc/profile.d and /etc/bash_completion.d
- you don't have to create symlinks to binaries, if path will be set correctly
- man pages are installed in wrong place
- file ownership of some files is wrong

This is a long list, but I've prepared for you a version of this package that has some of it fixed (not all):

- (

Try downloading this version and building, then use "namcap" command on resulting package to see list of remaining issues. You won't be able to fix those .jar issues, because namcap does not see virtual dependency (java-environment, which can point to many versions of java JDK), but it should be enough as a hint of how to proceed.

Will you be able to update this?