Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 49c6a2b5 authored by Doug Zongker's avatar Doug Zongker
Browse files

fix build fingerprint: dev-keys vs test-keys 

The fingerprint should only say dev-keys if it's actually using custom
keys; builds with the old default (from build/target/product/security)
should still say test-keys.

Change-Id: Ib8c662c348cf63f5db47e2f8f81bc3246cb15fdc
parent ad4142cc

core/Makefile

+9 −2
Original line number Original line Diff line number Diff line
@@ -71,9 +71,16 @@ BUILD_VERSION_TAGS := $(BUILD_VERSION_TAGS) 
ifeq ($(TARGET_BUILD_TYPE),debug)

ifeq ($(TARGET_BUILD_TYPE),debug)

  BUILD_VERSION_TAGS += debug

  BUILD_VERSION_TAGS += debug

endif

endif

# Apps are always signed with dev keys, and may be re-signed in a post-build

# The "test-keys" tag marks builds signed with the old test keys,

# step.  If that happens, the "dev-keys" tag will be removed by that step.

# which are available in the SDK.  "dev-keys" marks builds signed with

# non-default dev keys (usually private keys from a vendor directory).

# Both of these tags will be removed and replaced with "release-keys"

# when the target-files is signed in a post-build step.

ifeq ($(DEFAULT_SYSTEM_DEV_CERTIFICATE),build/target/product/security/testkey)

BUILD_VERSION_TAGS += test-keys

else

BUILD_VERSION_TAGS += dev-keys

BUILD_VERSION_TAGS += dev-keys

endif

BUILD_VERSION_TAGS := $(subst $(space),$(comma),$(sort $(BUILD_VERSION_TAGS)))

BUILD_VERSION_TAGS := $(subst $(space),$(comma),$(sort $(BUILD_VERSION_TAGS)))





# A human-readable string that descibes this build in detail.

# A human-readable string that descibes this build in detail.