Package Details: google-chrome-dev 133.0.6847.2-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.44
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-11-21 19:42 (UTC)

Dependencies (12)

Required by (40)

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 .. 68 69 70 71 72 73 74 75 76 77 78 .. 91 Next › Last »

Weegee commented on 2011-01-20 20:35 (UTC)

Nah, I've built the package with makepkg (using the tarball), but it still didn't work :/

t3ddy commented on 2011-01-20 19:50 (UTC)

@Weegee maybe you've got the same problem that had sjakub i.e. yaourt cache I've decided to revert back to the original /opt/google/chrome instead of /opt/google-chrome because it seems that google's apps are all installed into /opt/google

Weegee commented on 2011-01-20 19:47 (UTC)

By the way, why doesn't "Make Google Chrome My Default Browser" actually make Google Chrome my default browser? If I start Chrome from within the terminal, I just get "which: no google-chrome in (/opt/google-chrome)" when I click on the button in the settings tab :(

t3ddy commented on 2011-01-20 10:43 (UTC)

Updated to 10.0.642.2. I've decided to revert back to the original directory, so now it's again in /opt/google/chrome. I don't think that anything cares where chrome is installed, but if also other google's apps are into /opt/google, probably also chrome should be there. I've also removed the directory /usr/lib from the pkgbuild since nothing was put in it and the optdependency moonlight has been removed, since I think is more than a year that a package with that name doesn't exists.

t3ddy commented on 2011-01-19 21:22 (UTC)

I'll do what you prefer, since for me it makes no difference at all.

Det commented on 2011-01-19 16:48 (UTC)

@sjakub, maybe you shouldn't post everything so quickly so that you wouldn't need to delete these posts afterwards either. In addition you would've seen t3ddy's response to you where he already told you why he changed the install dir. As for my stance about this, atm, you can't find a single "thing" that assumes Google Chrome is installed to "/opt/google". Nothing looks for it in there and nothing cares it's in there. I originally made the change because I had no idea that all Google stuff would/should be installed there. I just figured it was redundant to have a folder for Chrome where inside you got another folder that then would have the actual program - as such I changed the dir. Frankly, I don't think anybody even cares where Chrome is installed (as long as it just works) but it wouldn't be all bad idea to keep all the Google stuff in a single directory - as upstream wants. T3ddy's decision.

sjakub commented on 2011-01-19 16:19 (UTC)

I am wondering if it is going to cause problems. All other Google packages go to /opt/google/*. Also, since this is standard google's location, some things might assume it's there. Why did you want it Det?

t3ddy commented on 2011-01-19 16:14 (UTC)

Det has made the proposal, personally I had nothing counter and none else has said anything, so the change has been made.

sjakub commented on 2011-01-19 15:46 (UTC)

Sigh. No, you're right. I reinstalled everything and it was still wrong, but it was due to yaourt's caching :/ When I grabbed the tarball of this AUR package and did everything manually, just in case, it was fine. Sorry for that :( As a side note - why do you move it from /opt/google/chrome to /opt/google-chrome?

« First ‹ Previous 1 .. 68 69 70 71 72 73 74 75 76 77 78 .. 91 Next › Last »