pub fn cache_key_suffix_with_extra(extra: Option<&str>) -> StringExpand description
Two-segment cache key suffix accounting for an optional
--extra-kconfig fragment.
The suffix uses TWO segments instead of folding both inputs into one hash:
extra = None→kconfig_hash()only — byte-identical tocache_key_suffix, so paths that don’t expose--extra-kconfig(test / coverage / shell / verifier) keep resolving the existing keyspace and pre-1.0 cached kernels are not orphaned.extra = Some(content)→{kconfig_hash()}-xkc{extra_hash}, makingkernel listself-describing: a reader can see at a glance which entries carry user extras and which are pure baked-in builds. Different extra content yields differentxkc{...}segments, so cache discrimination across distinct--extra-kconfiginvocations is structural rather than collapsed into a single opaque hash.