Support ADB product keys purging with a dedicated flag

Instead of checking the build variant look for the value of a dedicated
flag to decide if we need to do the purging. The value of
RELEASE_BUILD_PURGE_PRODUCT_ADB_KEYS is set to true on user and false on
userdebug/eng across all releases. Because of that this patch does not
bring any functional changes.

BUG: b/373580227
Test: Add $(warning foo) to the conditional block. Verify that the output
      of lunch husky-${aosp_current,trunk_staging}-{user,userdebug,eng}
      is as expected.

Change-Id: Ice6042025e9d2767e3eee158960eaab46f9b7fd4
1 file changed
tree: a1036285bd654a5bc8386cd7f0291cfd361e297c
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. Usage.txt
README.md

Android Make Build System

This is the Makefile-based portion of the Android Build System.

For documentation on how to run a build, see Usage.txt

For a list of behavioral changes useful for Android.mk writers see Changes.md

For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.

This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.