On Tuesday 2020-10-20 23:53, Aaron Puchert wrote:
Recently I got a bug report  and I'm not sure if and what I should do
about it. Background is that we have llvm (including subpackages) in
multiple versions in the distributions, because major releases come out
about twice a year and we're not in a situation where all dependencies
work (or claim to work) with the same major version.
So there is for example llvm7, llvm8, llvm9, llvm10. Additionally we
have a metapackage llvm that just requires the newest versioned package,
in this case llvm10, and doesn't contain any files itself. Now some of
the subpackages can coexist, but others cannot, most notably the -devel
packages. So if you happen to have llvm-devel installed (which currently
requires llvm10-devel), you will soon get a conflict on zypper dup: the
new llvm-devel = 11.0.0 will require llvm11-devel, but that conflicts
with the existing llvm10-devel.
Unless you model llvm like gcc where libstdc++6-devel-gcc10 can coexist with
libstdc++6-devel-gcc11, the conflict-on-dup is desirable because you wouldn't
want to force an autoresolution on the user in this matter.
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org