I had a similar problem. I used an svn checkout. The entrire
third_party/cygwin directory went missing in the tarball.
Also, I suggest aria2c to download the tarball in the future which is
better than the browser.
On Feb 4, 10:33 am, Evan Martin <e...@chromium.org> wrote:
> On Wed, Feb 4, 2009 at 10:31 AM, noemata <ma...@noemata.org> wrote:
> > Surely, it's not that hard to have three sets of archives that provide
> > a complete snapshot of a working build environment. Internal to
> > Google, you must gen these anyways, so what's the issue? All such
> > archives should deliver a built version of Chromium to the recipient
> > so they can fire up the tests. I see this as the most basic goal of
> > the tar archive. Second to that is actually building it.
>
> I agree with all of your points but this one: part of the reason the
> tarballs are so often wrong or out of date is that nobody within
> Google uses them.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
