Package Details: chromium-snapshot-bin 133.0.6838.0.r1383276-1

Git Clone URL: https://aur.archlinux.org/chromium-snapshot-bin.git (read-only, click to copy)
Package Base: chromium-snapshot-bin
Description: The open-source project behind Google Chrome (Latest Snapshot)
Upstream URL: https://build.chromium.org
Keywords: browser web
Licenses: BSD
Provides: chromium-snapshot
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 498
Popularity: 0.51
First Submitted: 2015-04-20 12:12 (UTC)
Last Updated: 2024-11-15 11:35 (UTC)

Pinned Comments

Det commented on 2017-03-30 10:20 (UTC) (edited on 2017-12-13 23:06 (UTC) by Det)

✔ Do not flag this package out-of-date.

It updates automatically on each install.

Latest Comments

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 31 Next › Last »

xyproto commented on 2011-04-22 15:56 (UTC)

I could not find "ttf-hannom-usong", but I did find "ttf-hannom" (optdepends).

<deleted-account> commented on 2011-04-22 09:20 (UTC)

@jwhendy, @Det: The makepkg users can use --forcever=<whatever-version-was-working-fine> option to build and install any old/working version available at upstream/build site. @jwhendy: I think, you missed you're playing with a (pre-rlease) beta build, plz don;t expect stability and remained prepared for a bumpy road ahead when using/testing beta/alpha (pre-release) builds. IMHO, I and the upstream are providing these builds for testers only; for feedback, bug reports and, or feature request which users/testers must/should pass directly on to upstream developer's or site.

Det commented on 2011-04-22 05:32 (UTC)

@jwhendy, well, since Chromium gets updated like once every hour (see: http://build.chromium.org/f/chromium/snapshots/chromium-rel-linux-64/) are you aiming for to have the absolute latest build or just any build that has a bumped version number (which is done like once a day or so)? What other people do with this package is that whenever they wanna update it they just reinstall it (no need to remove it - just install it 'over' the former one). If you do not need to edit the PKGBUILD when updating you can also use Yaourt's "--noconfirm" flag to automatically pass all the questions and confirmations (be careful with this though - some packages might do bad things when the PKGBUILD is not reviewed beforehand).

jwhendy commented on 2011-04-21 18:29 (UTC)

Is there any way to force an upate whenever chromium is updated? Since this simply points at the LATEST link in their repos, it seems that this package is only updated if the owner does something, for example with the PKGBUILD. To illustrate why this is nice, 12.0.740.0 had broken spell checking (see here: http://tinyurl.com/5vnhosa). The bug report says that 12.0.742.0 fixed this, but even though I was running 12.0.740.0 and they are now at 12.0.744.0, yaourt showed no updates available with 'yaourt -Syu --aur.' I just did 'pacman -R chromium-browser-bin' and then 'yaourt chromium-browser-bin' to reinstall, and the problem is now fixed. But I wonder if there's a way to automatically flag an update when a new version comes out? This would be helpful for packages that point at a static link and thus can function for months without any changes to PKGBUILD or *.install files. Or are others already doing this somehow and I'm just behind the ball?

jwhendy commented on 2011-04-21 18:28 (UTC)

Is there any way to force an upate whenever chromium is updated? Since this simply points at the LATEST link in their repos, it seems that this package is only updated if the owner does something, for example with the PKGBUILD. To illustrate why this is nice, 12.0.740.0 had broken spell checking (see here: http://tinyurl.com/5vnhosa). The bug report says that 12.0.742.0 fixed this, but even though I was running 12.0.740.0 and they are now at 12.0.744.0, yaourt showed no updates available with 'yaourt -Syu --aur.' I just did 'pacman -R chromium-browser-bin' and then 'yaourt chromium-browser-bin' to reinstall, and the problem is now fixed. But I wonder if there's a way to automatically flag an update when a new version comes out? This would be helpful for packages that point at a static link and thus can function for months without any changes to PKGBUILD or *.install files. Or are others already doing this somehow and I'm just behind the ball?

tokland commented on 2011-04-08 14:53 (UTC)

Was anyone able to fix the icon problem for gnome/xfce? (I tried the solution proposed for kde, with no luck). I've seen no icon in the taskbar for 2 or 3 weeks (using 80922 now).

misc commented on 2011-03-27 13:07 (UTC)

I see, old habits die hard. :) curl, however, really is more advanced than wget: http://daniel.haxx.se/docs/curl-vs-wget.html Thanks for the info on $QUIET.

<deleted-account> commented on 2011-03-25 16:57 (UTC)

@misc, ok, that did the trick; I, indeed, am more used to wget (Debian/ArchLinux) and fetch (FreeBSD). I use the same PKGBUILD to repackage chromium-browser for Debian also; the $QUIET was '-q' for wget and can/shall be '-s' for curl :)

misc commented on 2011-03-25 10:41 (UTC)

Ah, you mean the other wget command? I missed that, my bad. Its curl equivalent is: curl http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/LATEST -s -o - -L Still, what does the $QUIET mean/contain? I failed to find it in any of Arch's documentation. It's also apparently simply empty?

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 31 Next › Last »