In AOSP those are merged already.
The main reason of the merge is, the source of the repositories is Chrome, and those should use the same revision conceptually. Merging those simplifies the uprev situation.
Chrome OS should also follow the situation.
Then, the uprev of the libs can be simpler.
Plans:
- Copy files from aosp/external/libmojo into aosp/external/libchrome.
- For that purpose, it is necessary to uprev libchrome to the ToT.
- Merge build rules.
- Remove libmojo ebuild, and build libmojo as part of libchrome package.
- libmojo uses crypto. So it will see crypto USE flag.
- Remove libmojo repository from repo manifest.
Note:
This approach may introduce libmojo library into the boards, which may not yet use libmojo.
However, considering servicification, and several new services already start using Mojo, so I think it is not the big problem.
If it is really problematic, we can introduce default-enabled mojo USE flag, and disable it on specific boards explicitly.
Comment 1 by hidehiko@chromium.org
, Nov 29