On Fri, May 1, 2009 at 1:34 PM, Marc-Antoine Ruel <mar...@chromium.org>wrote:

> gcl, gclient and friends are moving from
> http://src.chromium.org/svn/trunk/depot_tools/ to
> http://src.chromium.org/svn/trunk/tools/depot_tools/
>
> To help you with the switch, there is now a little script to switch
> automatically. Just run **
>    *convert_depot_tools*
> to convert the depot_tools to the new checkout. Warning: the output of this
> tool isn't nice. If anything fails, just checkout manually:
>    *svn co 
> **http://src.chromium.org/svn/**trunk/tools/depot_tools*<http://src.chromium.org/svn/trunk/tools/depot_tools>
> The end result is the same.
>
>
> The far biggest advantage is that there is only one place for all the
> scripts (no more platform specific) and you can now send patches directly
> from your depot_tools; e.g. no need to do a separate checkout and run scons
> anymore.
>
> The old depot_tools is scheduled to be removed on May 12, 2009 and you will
> be upgraded *automatically* next time you run gclient after that date.
>
> Windows-only side-effects:
>
>    - It won't install svn client nor python if they are found in %PATH%.
>    - If you used svn lately, the old depot_tools version was upgraded to
>    1.6. If you have svn 1.5 in your %PATH%, you may have trouble working with
>    your checkout. Just removing your old client from the path and run "gclient
>    help" again.
>
>
I'm confused by these last bullet points.  It is quite common for people to
have /usr/bin/svn on their $PATH when running under cygwin.  It was a goal
of depot_tools to provide the right version of svn regardless of what
version of svn might exist on $PATH already.  This is important because
/usr/bin/svn might be the wrong version or might be compiled for unix (LF
line endings instead of CRLF).  How do you avoid all of these problems?

-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