Description of problem: File conflicts with libkipi (listed below) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: file /usr/share/icons/hicolor/128x128/apps/kdcraw.png from install of kdegraphics-4.0.83-1.fc10.i386 conflicts with file from package libkdcraw-0.1.4-1.fc10.i386 file /usr/share/icons/hicolor/32x32/apps/kdcraw.png from install of kdegraphics-4.0.83-1.fc10.i386 conflicts with file from package libkdcraw-0.1.4-1.fc10.i386 file /usr/share/icons/hicolor/48x48/apps/kdcraw.png from install of kdegraphics-4.0.83-1.fc10.i386 conflicts with file from package libkdcraw-0.1.4-1.fc10.i386 file /usr/share/icons/hicolor/64x64/apps/kdcraw.png from install of kdegraphics-4.0.83-1.fc10.i386 conflicts with file from package libkdcraw-0.1.4-1.fc10.i386 file /usr/share/icons/hicolor/128x128/apps/kipi.png conflicts between attempted installs of kdegraphics-4.0.83-1.fc10.i386 and libkipi-0.1.6-1.fc10.i386 file /usr/share/icons/hicolor/16x16/apps/kipi.png conflicts between attempted installs of kdegraphics-4.0.83-1.fc10.i386 and libkipi-0.1.6-1.fc10.i386 file /usr/share/icons/hicolor/22x22/apps/kipi.png conflicts between attempted installs of kdegraphics-4.0.83-1.fc10.i386 and libkipi-0.1.6-1.fc10.i386 file /usr/share/icons/hicolor/32x32/apps/kipi.png conflicts between attempted installs of kdegraphics-4.0.83-1.fc10.i386 and libkipi-0.1.6-1.fc10.i386 file /usr/share/icons/hicolor/48x48/apps/kipi.png conflicts between attempted installs of kdegraphics-4.0.83-1.fc10.i386 and libkipi-0.1.6-1.fc10.i386 Expected results: Additional info:
I'll take care of this.
stage 1: fix runtime conflicts, -devel conflicts remain (%_libdir symlinks, pkgconfig).
Re-opening, pending -devel fixes.
-devel symlinks are fixable (using similar hacks such as in kdegames), but I'm stumped what to do with the pkgconfig files. Ideas? Suggestions?
We could require setting a nonstandard PKG_CONFIG_PATH. But I wonder if it is really worth it in this case.
Evil idea, since nothing that I know-of even uses the kde4-versions of these libraries, we could (temporarily?) omit their conflicting -devel parts.
But the KDE 4 Digikam will surely use them? (But will we still need the KDE 3 versions when we'll have KDE 4 Digikam?) Otherwise, only Gwenview (which is in kdegraphics itself, so it doesn't need a kdegraphics-devel), I don't think anything can use them yet.
Uh, mixed up formulations there, I mean: Otherwise, other than Gwenview (which is in kdegraphics itself, so it doesn't need a kdegraphics-devel), I don't think anything can use them yet.
Cool, looks like omitting the kde4-devel bits for F-9 is doable. Moving forward with F-10+, I'm pretty sure we can drop the kde3-devel bits, and other related apps needing kde4 upgrades will include kipi-plugins, kphotoalbum, showimg.
If the libs are very incompatible, shouldn't the .pc file get a rename to include a version number?
In a perfect world, yes, but that's only if upstream has the means and intention to support parallel-install of said versions.
alright, implemented ideas from comment #9 into kdegraphics-4.0.99-2