No, it doesn't.  I agree that a safesync URL would be awesome.
-Darin

On Mon, May 11, 2009 at 10:46 AM, Alex Russell <slightly...@google.com> wrote:
>
> Does green builder output for this bot get archived? I ask because it
> would be nice to be able to specify a safesync URL for gclient.
>
> Regards
>
> On Mon, May 11, 2009 at 10:16 AM, Darin Fisher <da...@chromium.org> wrote:
>>
>> It is now fairly easy to develop Chrome using tip-of-tree WebKit.
>>
>> First before doing anything, you should make sure that the canary bot
>> is green (at least the compile step):
>> http://hae14.jail.google.com:8016/waterfall?builder=Webkit%20(webkit.org)
>>
>> Then, create a .gclient file like so:
>>
>> solutions = [
>>  { "name" : "src",
>>    "url" : "http://src.chromium.org/svn/trunk/src";,
>>    "custom_deps" : {
>>      'src/third_party/WebKit': 
>> 'http://svn.webkit.org/repository/webkit/trunk',
>>      'src/third_party/WebKit/JavaScriptCore': None,
>>      'src/third_party/WebKit/WebCore': None,
>>      'src/third_party/WebKit/WebKitLibraries': None,
>>      'src/third_party/WebKit/WebKit/mac': None,
>>      'src/webkit/data/layout_tests/LayoutTests': None,
>>    }
>>  }
>> ]
>>
>> If you are starting from a clean slate, you will need to run "gclient
>> config http://src.chromium.org/svn/trunk/src"; to generate a default
>> .gclient file.
>>
>> NOTE: If you have commit access to Chromium, and want to commit to
>> Chromium from this checkout, then be sure to change
>> http://src.chromium.org/svn/trunk/src appropriately.
>>
>> After gclient sync, you will be left with a normal working copy of
>> WebKit under src/third_party/WebKit.  You can now prepare WebKit
>> patches for sending to bugs.webkit.org from here, and if you have
>> commit access to svn.webkit.org, you can even commit from here :-)
>>
>> Regards,
>> -Darin
>>
>> >
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to