Chromium proposal

From ArchWiki

Jump to: navigation, search

This is the wiki page for the proposal of chromium packages that shall be in aur.

  • chromium-browser-svn - building from source.

This has the right name and should not be deleted.

  • chromium-snapshot - package based on googlebot
  • chromium-ppa - package based on builds from ubuntu ppa

Those two doesn't need to be named like this. I'm opened to suggestion. I want that those packages, even the name will not be like this, to have proper descriptions about the source of the binary, building from the same PKGBUILD both architecture.


Panos Filip (Flamelab)

My suggestions:

Three PKGBUILDs in all.

1. chromium-browser-svn: It already exists on AUR. It is the only one that needs no care, it builds Chromium browser from source.

Now the two ones from build.chromium.org and ppa.launchpad.

They are both created from the svn source. The one is a zipped chromium browser (google buildbot), the other a Ubuntu specific deb.

The goals are: two different PKGBUILDs for each one that will automatically find the latest zip or deb and download the 32bit or 64bit one according to system's $CARCH variable.

2. The Googlebot's chromium PKGBUILD should be called: chromium-snapshot, even though the zip is called chrome-linux (we shouldn't care for that)

3. The PPA's chromium PKGBUILD should be called: chromium-snapshot-ppa, even though the deb is called differently (we shouldn't care for that either).

Issue: All the three of them are getting the pkgver when they are built, so AUR won't recognise their pkgver when it parses the PKGBUILDs.



PKGBUILD suggestions

A. chromium-snapshot

1. PKGBUILD.

The current one's on AUR download only 32bit or 64bit zips on different PKGBUILDs. We want only one PKGBUILD, that will follow system's $CARCH and automatically download the zip.


Stefan Husmann:

Rename package based on googlebot to chromium-bin

Rename package based on ubuntu package chromium-ubuntu-bin

I would reduce to actually one package build from sources and one binary package. The binary package should on the long hand be chromium-bin, but now technical reasons let me vote to keep chromium-ubuntu-bin (it is build with libjpeg 7). If chromium-bin switches to libjpeg 7 one day, chromium-ubuntu-bin should be removed from AUR.

Alternatively, if a TU wants to do that, we can move a source-based PKGBUILD to [community]. But since it seems to bee quite unstable, this needs a seperate proposal.

^^^Answer from *Panos Filip* --> Note: "chromium-bin" (the googlebot) is in fact the one built with libjpeg7. "chromium-ubuntu-bin" (the deb) is built with libjpeg6. When Ubuntu 9.10 is released, it will be possibly converted to libjpeg7.

^^^Answer from *Stefan Husmann* --> Okay, I got it the other way around. But then I see no point to keep the ppa stuff.

^^^Answer from *Panos Filip* --> Neither do I. I suggest the deb one too, since some people seem to find it *better*. It is better to have only two (the googlebot's and the svn)

^^^Answer from *Biru Ionut* --> I suggest both to make users happy and made them not to update any other versions of chromium. I like the names that Stefan suggested

^^^Answer from *Balwinder S Dheeman* --> I was not aware on this proposal, so I recently submitted one named chromium-browser-latest; It works on our devel packaging scheme and will/can package and download google buildbot binaries based on user's $CARCH.

^^^Answer from *Vishal Ravishankar* --> I see no point of sourcing from the debs. SVN and Googlebot is the way to go!


Gen2ly:

My two cents too would be chromium-bin and chromium-svn. The '-bin' seems like a good idea when potential building a large package from the AUR. I would think that the googlebot version be a preffered version (I've tried both ubuntu and googlebot and they seem equivocal) because it be a more 'direct' build (i.e. less patchs).

Personal tools