I thought the point of the tarball was to bootstrap the process, not to
remove the gclient dependencies. Doing a full checkout via gclient can be
slow (lots of requests for lots of files) and taxing on our server (same
reason). Having some base from which to start speeds it up and reduces load
on the server. I don't think we ever had a hard requirement that the tarball
be everything one would ever need, it just happened that the first versions
did happen to be so.
-Ian
On Tue, Feb 3, 2009 at 9:57 PM, Nicolas Sylvain <nsylv...@chromium.org>wrote:
>
>
> On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson <bre...@chromium.org> wrote:
>
>>
>> On Tue, Feb 3, 2009 at 9:05 PM, <t...@chromium.org> wrote:
>> > What evan means is that after downloading the tar ball, you need to run
>> > gclient sync to get all the platform specific dependencies.
>> >
>> > We recently started generating the source tar ball on a regular basis
>> and
>> > it doesn't include all the Windows and Mac dependencies from the
>> > src/third_party directory. Running gclient sync will download these
>> > platform specific dependencies for you.
>>
>> In that case, the build instructions are out of date. I updated the
>> getting-the-code page to reflect that this is now required.
>
>
> If this is now required, we screwed up somewhere. The goal of the tarball
> is mainly to give an easy way for people to download and build chromium. If
> they need to call gclient sync, it defeats the purpose.
>
> Are you sure we really need that?
>
> Nicolas
>
>
>>
>>
>> Brett
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
