Add a --unmanaged flag to gclient config to allow the main solution to be unmanaged by the scm.

Add a --unmanaged flag to gclient config to allow the main solution to be unmanaged by the scm.

The dependencies will continue to be managed.  A new flag is present in the .gclient file
to control this behavior.

[nsylvain, 2011-08-27 23:59:17]

Adding dpranke and fischman in CC. They can tell if this will be useful to them
or not.

(Tests will be added if there is a general agreement that this patch is
interesting enough to be committed)

[Ami GONE FROM CHROMIUM, 2011-08-28 00:06:48]

On 2011/08/27 23:59:17, nsylvain wrote:
> Adding dpranke and fischman in CC. They can tell if this will be useful to
them
> or not.
> 
> (Tests will be added if there is a general agreement that this patch is
> interesting enough to be committed)

Assuming this will enable me to go back to the workflow I described in 
http://code.google.com/p/chromium/issues/detail?id=89100#c6 but keep
UsingNewGit, I'd like that a lot.

[nsylvain, 2011-08-28 00:59:51]

this is indeed my attempt at that.  With this you'll have to manage updating
src/ manually (on all branches). Gclient will be used only to parse the DEPS
file and fetch/update the deps.

If you end up wanting gclient to update src/, then you might be able to use
gclient --revision src@HEAD, but I haven't tried that yet.

[Ami GONE FROM CHROMIUM, 2011-08-28 01:44:09]

SGTM

[M-A Ruel, 2011-08-28 13:03:31]

http://codereview.chromium.org/7777002/diff/1/gclient.py
File gclient.py (right):

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode335
gclient.py:335: None, self.deps_file, should_process))
So it's not inheritable?

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode401
gclient.py:401: scm = gclient_scm.CreateSCM(self.parsed_url, self.root_dir(),
self.name)
I'd modify it here instead. I'd probably make a member private function so you
can use the same code for line 236 too. I wouldn't touch gclient_scm.py, it
doesn't need to know.

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode984
gclient.py:984: parser.add_option('--unmanaged', action='store_true',
Why add the flag if it's accessible from .gclient?

[nsylvain, 2011-08-29 18:03:58]

http://codereview.chromium.org/7777002/diff/1/gclient.py
File gclient.py (right):

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode335
gclient.py:335: None, self.deps_file, should_process))
On 2011/08/28 13:03:31, Marc-Antoine Ruel wrote:
> So it's not inheritable?
Right

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode401
gclient.py:401: scm = gclient_scm.CreateSCM(self.parsed_url, self.root_dir(),
self.name)
On 2011/08/28 13:03:31, Marc-Antoine Ruel wrote:
> I'd modify it here instead. I'd probably make a member private function so you
> can use the same code for line 236 too. I wouldn't touch gclient_scm.py, it
> doesn't need to know.

I'll look into this

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode984
gclient.py:984: parser.add_option('--unmanaged', action='store_true',
because it's user friendly? Same reason we have --git-deps.

[cmp, 2011-08-29 19:01:59]

lgtm

[Dirk Pranke, 2011-08-29 20:56:13]

http://codereview.chromium.org/7777002/diff/1/gclient.py
File gclient.py (right):

http://codereview.chromium.org/7777002/diff/1/gclient.py#newcode984
gclient.py:984: parser.add_option('--unmanaged', action='store_true',
On 2011/08/29 18:03:58, nsylvain wrote:
> because it's user friendly? Same reason we have --git-deps.

It's unclear to me if both of these options are needed, and which will be
preferable. I imagine most people will have one checkout that is always managed,
but I actually sometimes switch between managed and unmanaged branches in a
single checkout.

[cmp, 2011-09-16 18:47:28]

Continued in http://codereview.chromium.org/7918027/.