News for hackers. Stuff that matters.

A comment on Chrome Release Cycle. Parent comment

Re:Chrome Release Cycle by w1ntermute on Monday January 10, 2011 @05:18PM (#2089972)
The funny thing is that from a Linux user's perspective, Google was simply providing a workaround for what should have been the OS's job. On Linux, Firefox's auto-updates are disabled so that the OS can handle that instead.

This is probably the best solution, as it gives you the most control over updates, and applies to all software system-wide. You're not forced to install updates at any time, and you can disable the notifications if you want.

[ Parent | on HN ]
Re:Chrome Release Cycle by dman on Monday January 10, 2011 @05:31PM (#2090013)
The update popup for extensions is still annoying though - even on linux.
[ Parent | on HN ]
Re:Chrome Release Cycle by w1ntermute on Monday January 10, 2011 @05:54PM (#2090047)
Like I said, you can disable that.
[ Parent | on HN ]
Re:Chrome Release Cycle by cookiecaper on Monday January 10, 2011 @08:17PM (#2090449)
Many distributions' version of Firefox comes with that disabled out of the box.
[ Parent | on HN ]
Re:Chrome Release Cycle by mtklein on Monday January 10, 2011 @08:21PM (#2090465)
And last I looked, that's how Chrome/Linux works too, at least on Ubuntu. When you download and install the deb, it'll set up apt sources so you get updates through the system.
[ Parent | on HN ]