Package Details: google-chrome-dev 133.0.6876.4-1

Git Clone URL: https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy)
Package Base: google-chrome-dev
Description: The popular web browser by Google (Dev Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 654
Popularity: 1.04
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-12-05 16:18 (UTC)

Dependencies (12)

Required by (41)

Sources (3)

Pinned Comments

gromit commented on 2023-07-19 17:01 (UTC) (edited on 2023-07-19 17:02 (UTC) by gromit)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Dev updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-unstable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 91 Next › Last »

Det commented on 2015-02-10 12:53 (UTC)

/usr/share/applications/google-chrome-unstable.desktop Look again.

scellow commented on 2015-02-10 12:49 (UTC)

It doesn't install the desktop entry ...

Det commented on 2015-02-03 22:12 (UTC)

Currently, nothing is failing validity check.

wicast commented on 2015-01-30 11:14 (UTC)

For md5sum of google-chrome-unstable_current_amd64.deb is now c7618adf2abe52acb55473eeccb4fa1b,please update the PKGBUILD.

<deleted-account> commented on 2015-01-30 02:08 (UTC)

amd64.deb is failing validity check.

wilberfan commented on 2015-01-30 01:59 (UTC)

The _i386.deb is failing the validity check for me.

Det commented on 2015-01-13 10:23 (UTC)

You are right, it's that way around.

hagabaka commented on 2015-01-13 09:13 (UTC)

@Det: when you quote "$VARIABLE" like the package currently does, multiple words in the variable will be treated as one single argument. When you don't quote it, the variable can be expanded to multiple arguments, split by space. Chromium implements CHROMIUM_FLAGS this way too, as you can see the last line of /usr/bin/chromium says exec /usr/lib/chromium/chromium $CHROMIUM_FLAGS "$@"

Det commented on 2015-01-13 09:04 (UTC)

@ruario, I finally checked, and both the download and decompression were slower than with .debs. @hagabaka, very few people use CHROME_USER_FLAGS, and many would be unaware why their flags work with Chromium but not Chrome: - https://www.google.com/search?&q="CHROME_USER_FLAGS" (19 results) - https://www.google.com/search?&q="CHROMIUM_USER_FLAGS" (1460 results) Also _with_ quotes is how you get the multiple arguments.

hagabaka commented on 2015-01-11 21:39 (UTC)

Actually, it should probably be sed -i 's/ "$@"/ $CHROMIUM_USER_FLAGS "$@"/' "$pkgdir"/opt/google/chrome-$_channel/google-chrome-$_channel Without quotes around $CHROMIUM_USER_FLAGS. This way it's possible to set multiple flags separated by space.

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 91 Next › Last »