What creates .gclient_entries?

[Nico Weber]

Hi,

I set up a new chrome checkout on a new windows box, using `fetch chromium`. I had to ctrl-c late during runhooks (during the msvc auto-install), but manually ran `gclient runhooks` to finish things later. The checkout looks correct, there's only one .gclient file, etc, but several commands print

"c:\src\chrome\.gclient_entries missing, .gclient file in paraent directory c:\src\chrome might not be the file you want to use."

I'm reasonably sure that it _is_ the file I want to use, but .gclient_entries really isn't there. What's that file for, and what's supposed to create it?

Thanks,

Nico

[Nico Weber]

Thanks! Rerunning `gclient sync` created the file (and had no other effects) and made the warning go away.

Maybe `gclient sync` could write .gclient_entries when it's done syncing and before running hooks – but it's admittedly a corner case.

On Wed, Aug 1, 2018 at 2:34 PM Edward Lemur <ehmal...@chromium.org> wrote:

Hi Nico,

You can ignore it.

It is created by gclient sync when it finishes executing [1]. It contains the entries that gclient synced so it can warn of dependencies that are no longer part of the checkout (because they were removed from DEPS).

When gclient is finding the root, it also checks that .gclient_entries exists [2], which is where the warning comes from.

[1] https://cs.chromium.org/chromium/tools/depot_tools/gclient.py?l=1605

[2] https://cs.chromium.org/chromium/tools/depot_tools/gclient_utils.py?l=637

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAMGbLiEgq6htu5ybkdmymsnAN5idxzM-66TSiAvmWTUXTEXJzg%40mail.gmail.com.