On Tuesday 2022-04-05 08:23, Richard Biener wrote:
A package set like {libgcc_s1-gcc7, libgcc_s1-gcc8, etc.} all have the *same* SO version. One could argue the policy is not applicable.
Note that the fact that we use suffixes at all instead of just building libgcc_s1 from more than one source rpm is due to (old?) restrictions of tooling which had no way to distinguish the different versions and ended up picking a random one to put on the media or to use for building packages with useforbuild.
The big issue is that two source packages in an OBS, pick Mesa and nvidiagfx if you need a thought example, could both be producing a libGL-1.0-1.1.rpm (first commit, first build attempt, and both having Version: 1.0). The same issue befalls gcc in principle, it just never manifests because gcc7 pretty much always has a different Version: field compared to gcc8.