Is there any chance of the -bin (precompiled) versions being hosted once an official release is made? I guess there's little reason for it as they're so easy to "compile" yourself, but it would simplify upgrading/maintenance for a number of users. I don't see google moving away from their custom build utilities any time soon, so unless someone forks chromium we're probably not going to get that a simplified build process. On Wed, Nov 18, 2009 at 6:01 PM, Daniel J Griffiths <ghost1227@xxxxxxxxxxxx>wrote: > hollunder@xxxxxx wrote: > >> On Wed, 18 Nov 2009 12:42:40 -0200 >> "Guilherme M. Nogueira" <guilherme@xxxxxxxxx> wrote: >> >> >> >>> On Wed, Nov 18, 2009 at 12:25 PM, Ionut Biru <biru.ionut@xxxxxxxxx> >>> wrote: >>> >>> >>> >>>> now is not the time. chromium doesn't have a stable release yet and >>>> the build process kinda suck. 10gb space for compiling chromium is >>>> something that cannot be forgot :) >>>> >>>> -- >>>> Ionut >>>> >>>> >>>> >>> WOW! Really?! >>> I had no idea compiling chromium needed that much space. >>> >>> >> >> >> One reason why I like Arch: >> It's easy to stay close to upstream, to work with them, and to kick >> butt if necessary. >> >> Regards, >> Philipp >> >> >> > I agree that we should have a TU-maintained build of chrome/chromium, but > as Ionut pointed out the current build process is a little ridiculous. Once > it has stabilized and matured a little bit more I will be happy to maintain > it. My wife uses it religiously so I have a good incentive to keep it clean > and current. :P >
