Comment # 17 on bug 1187214 from Michal Suchanek

It logically does not make sense to encode release description in random
packages.

rpm-config-SUSE is a collection of SUSE-specific rpm macros. They are not
specific to a SUSE version, they are specific to SUSE in general, and the
package should be buildable on any version (with the caveat that using a new
rpm-config-SUSE for some packages only can break things).

Specifically in the context of "Closing the Leap gap" it totally makes sense to
share the package between SLE and Leap, there is no real reason to branch it.

It could get the value of the macro at build time and re-encode it but where
would that come from?

Obvious candidates are project config and the release package which has the
purpose of describing the release.

Out of these only the release package is available for local builds or OBS
instances other than the SUSE one.

-> release package it is