[automerger skipped] Empty merge of Android 24Q2 Release (ab/11526283) to aosp-main-future am: ffa32a7560 -s ours

am skip reason: Merged-In I907a949535002de4c714568cbca85ffe5c015e3c with SHA-1 5ed958220b is already in history

Original change: https://googleplex-android-review.googlesource.com/c/platform/external/libbrillo/+/27145276

Change-Id: I0e180f9512817eab1759812e5d5065533d1786ae
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 158f5f4eba68adeaa20d94d9626b0ff92114be9e
  1. brillo/
  2. install_attributes/
  3. policy/
  4. Android.bp
  5. BUILD.gn
  6. libpolicy.ver
  7. METADATA
  8. MODULE_LICENSE_BSD
  9. NOTICE
  10. OWNERS
  11. PRESUBMIT.cfg
  12. README.md
  13. testrunner.cc
  14. testrunner_android.cc
README.md

libbrillo: platform utility library

libbrillo is a shared library meant to hold common utility code that we deem useful for platform projects. It supplements the functionality provided by libbase/libchrome since that project, by design, only holds functionality that Chromium (the browser) needs. As a result, this tends to be more OS-centric code.

AOSP Usage

This project is also used by Update Engine which is maintained in AOSP. However, AOSP doesn't use this codebase directly, it maintains its own libbrillo fork.

To help keep the projects in sync, we have a gsubtree set up on our GoB: https://chromium.googlesource.com/chromiumos/platform2/libbrillo/

This allows AOSP to cherry pick or merge changes directly back into their fork.