Package Details: google-chrome 129.0.6668.58-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2236
Popularity: 7.34
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (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 "Stable 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-stable" | \
     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 .. 144 145 146 147 148 149 150 151 152 153 154 .. 157 Next › Last »

Det commented on 2012-01-13 15:26 (UTC)

@ruario, yeah, when it's extracting the sources. Just like it'd do with a regular tarball.

ruario commented on 2012-01-13 13:47 (UTC)

@t3ddy: actually it seems makepkg now opens rpms (using bsdtar) for you! ;)

ruario commented on 2012-01-09 13:00 (UTC)

@t3ddy: Some other thoughts and/or possible improvements: Rather than using a fixed set icons and duplicating each of them in /usr you could symlink all available icons, e.g. # Symlinking icons to /usr/share/icons/hicolor/ for png in "$pkgdir/opt/google/chrome/product_logo_"*.png; do pngsize="${png##*/product_logo_}" mkdir -p "$pkgdir/usr/share/icons/hicolor/"${pngsize%.png}x${pngsize%.png}/apps (cd "$pkgdir/usr/share/icons/hicolor/"usr/share/icons/hicolor/${pngsize%.png}x${pngsize%.png}/apps/; ln -s ../../../../../../opt/google/chrome/product_logo_${pngsize} google-chrome.png) done You could also consider using the rpm as a source rather than the deb. The rpm is more generic, unlike deb packages which has several debianisms. For example "usr/share/menu/google-chrome.menu" (used only on debian systems) and the compressed changelog.gz (containing only a link and is really only provided to satisfy lintian, debian's package quality checking script). It is very easy to open an rpm on Arch. You do not need rpm2cpio as all Arch installs include bsdtar, which is provided by libarchive on which Arch's own pkgtools depend. In fact makepkg uses bsdtar itself to open tar files. bsdtar can open rpms directly without requiring any rpm components (e.g. bsdtar xf google-chrome-stable_current_amd64.rpm) If you need to read rpm packaging meta-data locally and don't have rpm installed you can just use "strings google-chrome-stable_current_x86_64.rpm | less". For you personal script that you use to update the PKGBUILD, this would tell you the latest version and build number: _verbld=$(wget -qO- http://dl.google.com/linux/chrome/rpm/stable/$(uname -m | sed 's/i.86/i386/')/repodata/other.xml.gz | zcat | awk -F\" '/-stable/ { print $10"-"$12 }') Thus making the direct download urls: http://dl.google.com/linux/chrome/rpm/stable/i386/google-chrome-stable-${_verbld}.i386.rpm http://dl.google.com/linux/chrome/rpm/stable/i386/google-chrome-stable-${_verbld}.x86_64.rpm Whether the deb or rpm is used the file "/etc/cron.daily/google-chrome" should be removed from Arch before packaging as it is a cron job to use Google's own rpm or deb repositories and hence is pointless on Arch. No rush and feel free to ignore them all. Just some ideas. ;)

t3ddy commented on 2012-01-09 12:42 (UTC)

ruario is right, I've got a script that acts on a template to make the pkgbuild. Now I don't have time to look at your suggestion, but I'll do asap. Thanks :)

ruario commented on 2012-01-09 12:16 (UTC)

> you can remove the unnecessary ones by just using the red/white cross buttons there. Done > he's not using any scripts. I beg to differ. It seems like he is his own script locally (not shared here) to create/update the PKGBUILD when updates to Chrome happen. Quotes from t3ddy, "I could change the pkgbuild if there's a way to predict the build number automatically, so I can change the script to read the version and modify the pkgbuild accordingly." "The problem is that chrome gets updated very frequently, so I'm using a script to do the job. Making your change will make the script useless and increase my work." At a guess, when he is notified (or becomes aware of an update by some other means), he runs a script which downloads the latest version for both architectures, checks the md5sums and updates the PKGBUILD. As I said, this makes perfect sense to me. I do the same with my own frequently updating PKGBUILD. His complaint previously about changing the URL to point to a specific build that this would make his life harder because it "will make the script useless".

Det commented on 2012-01-09 11:23 (UTC)

Well first off you can remove the unnecessary ones by just using the red/white cross buttons there. Also he's not using any scripts. The URL he's using doesn't change - just the file that gets downloaded.

ruario commented on 2012-01-09 09:25 (UTC)

@DetYes, apologies. I thought of each improvement a bit at a time. I wasn't international spamming. Anyway I don't think the idea would be to put it in the PKGBUILD itself. t3ddy said, "The problem is that chrome gets updated very frequently, so I'm using a script to do the job." I read that as him having some meta-script that creates/updates the PKGBUILD for him. This make sense as I do the same thing for opera-next (opera development builds). So presumably he would add the logic to his meta script, not the PKGBUILD itself.

Det commented on 2012-01-09 08:41 (UTC)

1) And that couldn't all fit in one post? 2) Also that's gonna look so great in the Sources section there.

ruario commented on 2012-01-09 08:06 (UTC)

@t3ddy: I suspect this is what you want your meta script to do: echo http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_$(curl -s https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-i386/Packages.gz | zcat | awk -F "[ -]" '/Package: google-chrome-stable/ { getline ; print $2"-"$3 }')_$(uname -m | sed 's/i.86/i386/;s/x86_64/amd64/').deb It will print back whatever is the link to the current stable version.

« First ‹ Previous 1 .. 144 145 146 147 148 149 150 151 152 153 154 .. 157 Next › Last »