Good Evening, no. Since the kde-package conflicts with the non kde version, nothing will break.
By the way, the package can be found at https://build.opensuse.org/package/show?package=LibEngsas&project=home%3Aengsas Regards, Joachim Langenbach On Wednesday 26 December 2012 16:10:28 Henri Gomez wrote: installing lib from /kde4/usr/lib could broke stuff in /usr/lib ? 2012/12/22 Joachim Langenbach <joac...@falaba.de> Hello, I'm trying to create a RPM, which produces three packages for a library. The first is the library without kde bindings, the second is the library with kde bindings and the third is the development package. I'm using the following file structure for installing: 1. library without kde installs into RPM_BUILD_ROOT (includes the header and other developing files) 2. library with kde installs into RPM_BUILD_ROOT/kde4 I choose this sepparation, because both libraries are building the libengsas.so file, with identical API, but different internal bindings. So applications, using libengsas, can link against one version of it and it is independent from the one, which the user has installed on the system. But I have not found a way to tell RPM in the "%files kde" that the directory /kde4/usr/lib must be installed at /usr/lib on the users machine, when installing the package. Is there a way, I can solve this problem? I'm appreciated for any help. Kind regards, Joachim Langenbach
signature.asc
Description: This is a digitally signed message part.
