Package Details: chromium-snapshot-bin 89.0-1

Git Clone URL: (read-only, click to copy)
Package Base: chromium-snapshot-bin
Description: The open-source project behind Google Chrome (Latest Snapshot)
Upstream URL:
Keywords: browser web
Licenses: BSD
Provides: chromium
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 499
Popularity: 0.75
First Submitted: 2015-04-20 12:12
Last Updated: 2020-11-16 23:33

Dependencies (11)

Required by (74)

Sources (12)

Pinned Comments

Det commented on 2017-03-30 10:20

Do not flag this package out-of-date.

It updates automatically on each install.

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

Det commented on 2015-08-04 22:30

Ok, so?

lucianoar commented on 2015-08-04 22:29

pkgver=45.0.2454.0.r338261 in the PKGBUILD, while current version in is 46.0.2472.0.r341720

Det commented on 2015-08-03 18:46

@lucianoar, doushite?

Det commented on 2015-06-24 11:47

TCGman commented on 2015-06-23 08:48

I just tried to install the package and it seems the checksums are wrong...
I got it working by changing them from :


to :


Det commented on 2015-05-17 21:19

No, like I said, there's a new build pretty much every hour [*]. You wouldn't want all of those anyway. Think of it as an hourly nightly. If you want specific releases, try chromium from [extra], or google-chrome(-beta/-dev) here in the AUR:

[*] Just compare the time stamps on:

deemde commented on 2015-05-17 21:14

Thank you for clarifying.
It did fetch 45.0.2405.0.r330310 for me upon reinstall right now.
Is there a way to automate the package-versioning to enable detection of new builds by package management?

Det commented on 2015-05-17 21:08

Yeah, it fetches the latest one, whenever you try. It won't be bumped here in the AUR every time, because there's a new build practically every hour.

deemde commented on 2015-05-17 21:07

Thank you for clarifying.
It did fetch 45.0.2405.0 for me upon reinstall right now.

Det commented on 2015-05-17 18:39

Yeah, well, this is just fetching the latest Google-built/tested build from their servers, and if a fix hasn't been committed all the way (or was reverted), then that's not this package's problem. You can flag this package if the build fails (say, source was moved, or file(s) mentioned in package() no longer exist).