commit 5f939f99ec17219ede032328edf8778d182c45ab
author Jiyong Park <jiyong@google.com> Wed May 01 16:18:14 2024 +0900
committer Jiyong Park <jiyong@google.com> Thu May 02 09:29:36 2024 +0900
tree 368b4c803eee75bf71ae475c7242d8d7938acc14
parent b0d12a730913dfaad9bea2ae81f5058d898aa996

Use no_full_install: true instead of installable: false

So far, we have used `instalable: false` to avoid collision with the
other modules that are installed to the same path. A typical example was
<foo> and <foo>.microdroid. The latter is a modified version of the
former for the inclusion of the microdroid image. They however both have
the same instalation path (ex: system/bin) and stem (ex: foo) so that we
can reference them using the same path regardless of whether we are in
Android or microdroid.

However, the use of `installable: false` for the purpose is actually
incorrect, because `installable: false` also means, obviously, "this
module shouldn't be installed". The only reason this incorrect way has
worked is simply because packaging modules (ex: android_filesystem)
didn't respect the property when gathering the modules.

As packaging modules are now fixed to respect `installable: false`, we
need a correct way of avoiding the collision. `no_full_install: true` is
it.

If a module has this property set to true, it is never installed to the
full instal path like out/target/product/<partition>/... It can be
installed only via packaging modules.

Bug: 338160898
Test: m
Change-Id: I0baa92efeedc2a8fb7aeb9d6b1da166e1c80d0c5