Hi,
I have submitted a *Chrome* CL adding a new device policy,
AFAIK I have to update the chromeos-base/protofiles ebuild to get the updated proto files / generated proto header in the Chrome OS chroot.
the components/policy.git repo looks fine and has the matching chunk of my CL :
while the chromeos/policy/proto.git repo looks stale, stuck 4 months ago:
So I have no idea what to put as new hashes in the EGIT_REPO_URIS of the ebuild.
I'm not sure I understand how those repositories are updated, the ebuild alludes they are 'read-only', so I imagine they are somehow cloned from the main chromium/src.git repo ?
Does somebody have more clues than me on this topic ?
Thanks,
--
Vincent