On Mon, 14 Oct 2013, Jan Engelhardt wrote:
On Monday 2013-10-14 16:17, Richard Biener wrote:
Well, package maintainers certainly have some control ;-) In fact, devel:gcc has the same issue that there are multiple libgcc binrpms that provide the same file. Fix it there, and it will autofix all other repos too.
I have fixed it for gcc47 and gcc48 and will not touch legacy GCC. IMHO this should have been fixed a level higher as requested in some Fate entry, but people chose to ignore that and instead suggest the setup we have now (%define product_libs_gcc_ver in your project config, yeah, and I didn't bother to do that properly for devel:gcc yet - tons of %if "%_repository" stuff required). Oh, and that "solution" doesn't "solve" the multiple packages with the same binaries in them issue but only the issue that we cannot follow the shared library policy (same binary package names from multiple source packages).
Is removing {the production of libgcc33} in gcc33.spec not sufficient? As in, killing the %files part and doing a rm -f in %install instead.
Sure, but that's not maintainable (you need it for SLE9). And how do you for example handle the introduction of a newer GCC in devel:gcc for people to install? Like if I'm on 12.1 (I am) and want to install gcc48 I actually _need_ the libgcc_s1 from gcc48, so I cannot remove it in the openSUSE_12.1 repo where gcc46 is the default (and thus its libgcc prevails). Believe me, we have thought about this a lot ;) Richard. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org