[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Chromium Browser Paralysis

In <[🔎] 20101016131902.25d8619a@snapdragon>, Morgan Gangwere wrote:
>On Sat, 16 Oct 2010 14:35:23 -0400 Jordan Metzmeier <> wrote:
>> I don't think advising against using Debian software is in the best
>> interest of Debian or its users.
>Providing debs of Chromium is like providing debs of Enlightenment's
>DR17 branch: Its out of date by the time the package is built.

You can say that about virtually any software with a large enough developer 
base.  While the number of commits might slow during a release, they don't 
stop.  So, unless you are building out of their VCS, you are "out-of-date" in 
some fashion.

Some projects make their more visible by automatically preparing new 
packages/installers out of their CVS on a nightly or better basis.  If the CPU 
cycles are available, you can even get into continuous integration flow, where 
each commit triggers builds, tests, packaging, etc. and only when that 
succeeds is the commit moved to a "stable" branch.

>As much as I like chromium (I use it as my default browser on Windows
>and Linux, and soon on Mac too) the release cycle is too fast to allow
>for appropriate packaging given the speed of Debian packaging.

I haven't used Chromium a lot, but I've been very happy with the Debian 
packaging.  In fact, the 6.x line is slated to be included in Squeeze and 
stably maintained for the lifetime of that release.
Boyd Stephen Smith Jr.                   ,= ,-_-. =.
bss@iguanasuicide.net                   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy         `-'(. .)`-'
http://iguanasuicide.net/                    \_/

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: