Overview
Request 777596 superseded
Initial GCC 10 submission, for switching the default runtime libraries
but not yet the default compiler for building packages. Adjust project
config like
# define which gcc package builds the system libraries
%product_libs_gcc_ver 10
...
# The following shlibs have the latest version built from GCC 9 sources
%product_libs_gcc_ver_libasan5 9
%product_libs_gcc_ver_libgo14 9
- Created by rguenther
- In state superseded
- Superseded by 779119
- Open review for openSUSE:Factory:Staging:N
Request History
rguenther created request
Initial GCC 10 submission, for switching the default runtime libraries
but not yet the default compiler for building packages. Adjust project
config like
# define which gcc package builds the system libraries
%product_libs_gcc_ver 10
...
# The following shlibs have the latest version built from GCC 9 sources
%product_libs_gcc_ver_libasan5 9
%product_libs_gcc_ver_libgo14 9
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
namtrac accepted review
dimstar_suse added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:55"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:adi:55"
dimstar added dimstar as a reviewer
As we intendf to switch the library-building GCC, this needs a ring0 staging
dimstar accepted review
licensedigger accepted review
ok
dimstar_suse added factory-staging as a reviewer
Being evaluated by group "factory-staging"
dimstar_suse accepted review
Unstaged from project "openSUSE:Factory:Staging:adi:55"
dimstar_suse set openSUSE:Factory:Staging:N as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:N"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:N"
superseded by 779119
(I'm not sure if the pp-gcc10 suffix is even right - shouldn't that be unsuffixed, as gcc_libs_ver is 10?
Nevertheless, the conflict with a 2nd package is a bad thing
The -pp packages are always suffixed. But what's a "first time" is that the latest symver of libstdc++ doesn't change between gcc9 (branch) and gcc10 ... I'll see how to fix this - going to be "interesting..."
So... currently we have those packages supplementing gdb and libstdc++6 = %{version} but they do not actually require libstdc++6 = %{version}. So it's possible for the user to forcefully install both. Now, if I add a requires to libstdc++6 = %{version} then the conflicts in that package kicks in and would prevent parallel install of both -pp packages. Unfortunately I'll have to adjust the gcc9 package in a similar way and the fallback mechanism for distros w/o (gdb and ..) style supplements will continue to be broken (we'll hit that with the gcc10 toolchain module for SLE12).
Would that work?
Otherwise I can do Provides: libstdc++6-pp Conflicts: libstdc++6-pp style. That's probably easier...
The Provides/Conflicts sounds like the least error prone and most straight forward approach.