We could make fully self-sufficient tarballs, but then we'd need three separate ones, since the three platforms have different dependencies. (Or we'd need to stick Mac and Linux developers with downloading a bigger tarball than they need.) I think it's fair to require a sync after downloading the tarball, since you'll need to have the tools working at some point. If you don't ever want to update your source code, you can use the "continuous" builds.
(For the moment, since the tarballs are generated arbitrarily at 2 AM, syncing to a working build is a good idea anyway. But I plan to change it to package up a known-green revision.) - Pam On Tue, Feb 3, 2009 at 9:57 PM, Nicolas Sylvain <[email protected]>wrote: > > > On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson <[email protected]> wrote: > >> >> On Tue, Feb 3, 2009 at 9:05 PM, <[email protected]> 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
