[aur-general] Status of the Chromium/Chrome packages on AUR

[Panos Filip]

On Sat, Sep 26, 2009 at 8:13 PM, Sven-Hendrik Haase <sh at lutzhaase.com>wrote:

> On 26.09.2009 18:49, solsTiCe d'Hiver wrote:
> > i don't know how much time is needed to compile chromium. but i guess at
> > least 1 or 2 hours ??
> > so i am not willing to take that much time to compile chromium every
> > time. so using a binary package is not a bad idea for me
> >
> >
> >
> The idea is to decide on a chromium package which will eventually be
> used in [community] so that you don't have to compile it. Obviously, a
> PPA based package is not a good choice here.
>

The svn/cvs/git etc packages rarely pass to [community] or even [extra].
Only when an official (buildable from source) Chrome browser or a stabilised
snapshot of Chromium are announced, they shall pass to [community] or
[extra]

The **best** PKGBUILD for Chromium is possibly the one that actually builds
it. The same thing for the other browsers (for example, Firefox).

The others exist because building Chromium takes too long, even on an
powerful machine.

---------

Someone told about the deb ones.

Actual differences between the ppa deb and zip from googlebot ? None. They
are both built from svn. The deb one has minor quality than the zip because
it is built with libjpeg6, and the zipped one with libjpeg7. Arch has
libjpeg7, so you don't need to install libjpeg6 from AUR.