https://bugzilla.novell.com/show_bug.cgi?id=731832

https://bugzilla.novell.com/show_bug.cgi?id=731832#c6


Markus K <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW
       InfoProvider|[email protected]            |

--- Comment #6 from Markus K <[email protected]> 2011-11-23 16:43:46 UTC ---
(In reply to comment #5)
> The problem is there is no such thing as stable branch of Chromium. Google
> release engineering is crap, because you can't tell if the release is a 
> feature
> release or bugfix release.
Well, the stable branch in always latest major version number -2.
So currently 15 is stable, 16 is beta, 17 is alpha.

> Markus, do you have some trick how to decide which version is "stable" enough
> for Factory? That would help greatly.

Well, after looking at Arch's PKGBUILD [1] it's actually very easy.
The tarball of the latest Chromium has exactly the same version number as
Google Chrome.
The latest stable version can either be automatically found out by parsing the
XML file http://commondatastorage.googleapis.com/chromium-browser-official and
then looking for the newest "LastModified" of major-2 (probably not worth the
effort writing a parser) or by simply grabbing the newest version number from
http://googlechromereleases.blogspot.com/search/label/Stable%20updates and
manually modifying the specfile every few weeks.

In specfile syntax the tarball can be acquired via 
http://commondatastorage.googleapis.com/chromium-browser-official/chromium-%{version}.tar.bz2

So as of today, the specfile would specify
"Version:        15.0.874.121"

And the latest stable version is 
http://commondatastorage.googleapis.com/chromium-browser-official/chromium-15.0.874.121.tar.bz2

[1]
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/chromium

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to