I’m trying to create a stand-alone RPM package of CopperSpice. Already have all of the Debian packaging done. I use this for RedDiamond and was previously thumping everything in under OPT. Now I’m busting the packages out into their own RPMs and putting them in proper system directories. I’m not a complete Newb to RPMBUILD, but I am a Newb to this error and how to fix it.
It’s not a “file” conflict. The default action for RPMBUILD (and one of the reasons I like it) is if you put /usr in your .spec file (and your build actually puts things there) is that it finds and does everything for you.
When I run
rpm -qpl my.rpm
on the generated rpm I see the following:
/usr/lib/.build-id/f7/5f0173fd01e2bb844e138f740b6d9db759153f /usr/lib/.build-id/f7/9ee405efa0679693826cb848042d8f1d7fee66 /usr/lib64 /usr/lib64/cmake /usr/lib64/cmake/CopperSpice /usr/lib64/cmake/CopperSpice/CopperSpiceBinaryTargets-release.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceBinaryTargets.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceConfig.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceConfigVersion.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceDeploy.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceLibraryTargets-release.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceLibraryTargets.cmake /usr/lib64/cmake/CopperSpice/CopperSpiceMacros.cmake /usr/lib64/cmake/CopperSpice/InstallMinGW.cmake /usr/lib64/copperspice /usr/lib64/copperspice/bin /usr/lib64/copperspice/bin/lconvert /usr/lib64/copperspice/bin/linguist /usr/lib64/copperspice/bin/lrelease /usr/lib64/copperspice/bin/lupdate /usr/lib64/copperspice/bin/rcc /usr/lib64/copperspice/bin/uic /usr/lib64/copperspice/plugins /usr/lib64/copperspice/plugins/imageformats /usr/lib64/copperspice/plugins/imageformats/CsImageFormatsSvg1.8.so /usr/lib64/copperspice/plugins/mediaservices /usr/lib64/copperspice/plugins/mediaservices/CsMultimedia_gst_audiodecoder1.8.so /usr/lib64/copperspice/plugins/mediaservices/CsMultimedia_gst_camerabin1.8.so /usr/lib64/copperspice/plugins/mediaservices/CsMultimedia_gst_mediaplayer1.8.so
The existence of /usr/lib64 should not be causing this error, but apparently is. Forcing people to do this:
is a recipe for disaster. Always was which is why the RPMBUILD default behavior became “include everything under the directory”
Is there a better work around that doesn’t require a user to -force an install?