Move "master" libchrome repository from AOSP to CrOS. |
||
Issue descriptionCurrently, libchrome is updated in AOSP first, then it is ported to CrOS. With the discussion in crbug.com/830940 , libbrillo's "master" is being moved into CrOS. I'd propose to move libchrome's master back to CrOS, too. - libbrillo depends on libchrome, too. If we keep maintaining libchrome in AOSP as master, while moving libbrillo's master to CrOS, we need local change in AOSP libbrillo at first, then port it back to CrOS libbrillo. It makes uprev procedure more complicated. - The code in ChromeOS is closer to chromium than AOSP. So, the update libchrome in ChromeOS should be simpler than what we now have in AOSP. It should help to make uprev more frequently. Non goal of this bug, but in future, we'd like to have PFQ, too. Note that, currently we are updating libchrome, so we should find a right timing.
,
Aug 14
It is not mandatory. Actually, we have diverged in CrOS and AOSP right now (AOPS's is newer). Though, practically, we'd like to use newer ones in both CrOS and AOSP. Focusing on ARC++, we'd need new libchrome for, at least, but not limited to, Mojo. Also, for those who write code in both CrOS and AOSP, checking versions and what are usable in each repo sounds like a headache. It's nice if these are (almost) same version to minimize it.
,
Jan 7
|
||
►
Sign in to add a comment |
||
Comment 1 by derat@chromium.org
, Aug 14