Out of date. @giniu's script reports the version at 0.9.32
Search Criteria
Package Details: google-cloud-cli 502.0.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-cloud-cli.git (read-only, click to copy) |
---|---|
Package Base: | google-cloud-cli |
Description: | A set of command-line tools for the Google Cloud Platform. Includes gcloud (with beta and alpha commands), gsutil, and bq. |
Upstream URL: | https://cloud.google.com/cli/ |
Keywords: | cloud gcloud gcp google sdk |
Licenses: | Apache-2.0 |
Conflicts: | google-cloud-sdk |
Provides: | google-cloud-sdk |
Replaces: | google-cloud-sdk |
Submitter: | PolarianDev |
Maintainer: | jvybihal |
Last Packager: | jvybihal |
Votes: | 188 |
Popularity: | 0.29 |
First Submitted: | 2023-03-08 09:33 (UTC) |
Last Updated: | 2024-11-20 07:51 (UTC) |
Dependencies (2)
- python (python37AUR, python311AUR, python310AUR)
- python-crcmod (optional) – [gsutil] verify the integrity of GCS object contents
Required by (15)
- arkade-bin (requires google-cloud-sdk) (optional)
- gcsfuse (requires google-cloud-sdk) (optional)
- google-cloud-cli-firestore-emulator
- google-cloud-cli-gke-gcloud-auth-plugin
- google-cloud-sdk-app-engine-java (requires google-cloud-sdk)
- google-cloud-sdk-app-engine-python (requires google-cloud-sdk)
- google-cloud-sdk-app-engine-python-extras (requires google-cloud-sdk)
- google-cloud-sdk-bigtable-emulator (requires google-cloud-sdk)
- google-cloud-sdk-cbt (requires google-cloud-sdk)
- google-cloud-sdk-datastore-emulator (requires google-cloud-sdk)
- k3sup-bin (requires google-cloud-sdk) (optional)
- porter-bin (requires google-cloud-sdk) (optional)
- python-google-earthengine-api (requires google-cloud-sdk)
- repman (optional)
- repman-git (optional)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 25 26 27 28 29 30 31 Next › Last »
zanegrey commented on 2014-09-21 20:31 (UTC)
justin8 commented on 2014-08-02 03:07 (UTC)
Can you please make this not include the appengine files. it makes it go from 21MB up to almost 200, not to mention it is already providing files that are in the google-appengine-* packages that have been around for years.
Please also fix up:
- Your broken python sed that just replacings things everywhere and has already been mentioned. something like this would do only the changes you actually want:
grep -rl 'python' "$pkgdir/opt/$pkgname" | xargs sed -i 's|#!.*python\b|#!/usr/bin/env python2|g'
find "$pkgdir/opt/google-cloud-sdk/bin/" -type f -maxdepth 1 -exec sed -i 's/CLOUDSDK_PYTHON=python/CLOUDSDK_PYTHON=python2/g' {} \;
- Symlink the binaries so that they are actually on the path and usable; unless you remove the appengine parts from this you will inadvertently create conflicts with the appengine packages. This will do it for you:
mkdir -p "$pkgdir/usr/bin"
find "$pkgdir/opt/$pkgname/bin" -type f -maxdepth 1 -printf "/opt/$pkgname/bin/%f\n" | xargs ln -st "$pkgdir/usr/bin"
Or just upload this pkgbuild that does it already:
http://storage.googleapis.com/justin8-files/public/google-cloud-sdk-PKGBUILD
The only namcap warnings from that package are somewhat ignorable now. If you remove the appengine dependencies you can change it to an any package instead of x86-64/i686, and there are 4 empty directories, but there is a chance that the oauth2-boto plugin needs those; I haven't used it before.
<deleted-account> commented on 2014-07-03 21:46 (UTC)
Instead of using sed to modify the source you can use:
export CLOUDSDK_PYTHON=/usr/bin/python2
giniu commented on 2014-06-23 20:04 (UTC)
Btw, you can use this:
curl -s https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz | tar -zxO google-cloud-sdk/lib/googlecloudsdk/core/config.json | grep '"version"' | sed "s/.*:.*\"\(.*\)\".*/\1/"
to check current version
giniu commented on 2014-06-23 19:56 (UTC)
Seems it only happened once, it is 0.9.27 now (version number is in RELEASE_NOTES and in file lib/googlecloudsdk/core/config.json)
numkem commented on 2014-06-23 19:13 (UTC)
Seems like the downloaded archive gets changed quite often while the filename or version doesn't.
I don't really know how we could keep up with their changes.
numkem commented on 2014-06-16 13:45 (UTC)
OK! This should be a pretty good version. I was using namcap before but I didn't really understand why it was complaining. With your explanations and some digging and fixed most problems.
giniu commented on 2014-06-14 14:11 (UTC)
Better with every version - though there are still some comments... sorry for that, I just want to help you get it right :) In short, use namcap - https://wiki.archlinux.org/index.php/namcap
- architecture of this package isn't "any", there are different libraries installed for 32 and 64 bits (look at stuff listed during install on stdout)
- you miss "!strip" option, it causes lots of errors during compilation like: "strip: ...: Unable to recognise the format of file" - this is common issue related to how "go" works - most go related packages in repos have this: https://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/liteide#n18
- consider downloading tar.gz instead of .zip - google provides both, but tar and gzip are in base, while unzip is not - also, if you switch you might not need to change permissions anymore (guess)
- when downloading, consider changing the name of stored file to include version number (see my example with double :: in name, that's how you change name) - it will help build automation scripts (if someone uses those) to get correct sources
- add maintainer tag so your name will be in it:
[giniu@raven3 google-cloud-sdk]$ namcap PKGBUILD
PKGBUILD (google-cloud-sdk) W: Missing Maintainer tag
- some other issues found with namcap:
1) your script to rename python into python2 does other things, there is no such thing as python22.5, probably it was legacy script for python2.5
google-cloud-sdk W: Referenced library 'python22.5' is an uninstalled dependency
google-cloud-sdk W: Referenced library 'python22.4' is an uninstalled dependency
2) and in other place it looks like it is cutting something out
google-cloud-sdk W: Referenced library 'bin' is an uninstalled dependency
3) there are empty directories and no correct flag package options:
google-cloud-sdk W: Directory (opt/google-cloud-sdk/platform/gsutil/third_party/gcs-oauth2-boto-plugin/third_party/retry-decorator) is empty
4) still LOT more files miss correct python version - you actually need to change python3 to python after changing python to python2, as it seems, and maybe add python as optional dependency. It needs looking into after you deal with python->python2 rename.
google-cloud-sdk E: Dependency python detected and not included (programs ['python', 'python3'] needed in scripts ['opt/google-cloud-sdk/platform/google_appengine/google/net/proto2/pytho
n/public/reflection.py', 'opt/google-cloud-sdk/platform/google_appengine/google/appengine/ext/mapreduce/api/map_job/datastore_input_reader.py', 'opt/google-cloud-sdk/platform/google_appe
ngine/google/appengine/cron/GrocParser.py', 'opt/google-cloud-sdk/platform/google_appengine/google/appengine/ext/db/djangoforms.py', 'opt/google-cloud-sdk/platform/gsutil/third_party/bot
o/boto/services/bs.py', 'opt/google-cloud-sdk/platform/google_appengine/google/appengine/tools/devappserver2/__init__.py', ........
numkem commented on 2014-06-12 13:04 (UTC)
I've made changes related to your comment. I've also used the new method of using mkaurball instead of makepkg -S
giniu commented on 2014-06-12 06:46 (UTC)
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/install.sh 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 install.sh. If you want to use install.sh 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 PKGBUILD
namcap (resulting file)
it will give you a lot of useful information.
Pinned Comments