(In reply to Franck Bui from comment #15) > (In reply to Ludwig Nussel from comment #12) > > (In reply to Dr. Werner Fink from comment #11) > > > On the other hand I'm wondering why the automagic requirement detections > > > from rpmbuild do not detect that the *.so links or linker scripts do require > > > some real libraries ;) > > > > That's a fair question but doesn't help in this case as the libs are in > > libsystemd0 which is already required explicitly in systemd-devel. > > Most -devel packages require their main package anyways, so unless there are > > specific reasons why sytemd-devel doesn't require systemd I'd actualyl try > > adding that requirement. > > That looks strange: installing systemd package as buildrequire and all its > dependencies simply to be able to use systemd.pc. That's a consequence of putting systemd.pc into the systemd package :-) If packages BuildRequire pkgconfig(systemd) the build system would likely choose systemd-mini instead though. Let me try to describe the problem again: 1. packages requiring systemd-devel and expecting systemd.pc to be installed 2. packages requiring systemd-devel and expecting all directories of systemd have an owner. AFAICS so far there are multiple possible solutions, e.g. a) put a Support: systemd in prjconfig and have systemd in all buildroots to mimic SLE => undesirable as it makes bootstrapping harder or impossible. Will for sure hurt later. b) fix all affected packages in SLE and Leap to BuildRequire: pkgconfig(systemd). Is an effort but solves 1) and 2) c) move systemd.pc back to systemd-devel. To also solve 2) systemd-devel additionally must own several directories where packages might install files into. d) make systemd-devel require systemd Pick your poison please :-) > I took a look at bluez package since you mentioned initially, and I don't > see why systemd.pc is needed. It wants to figure out where to install service files I suppose: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:42.2:Staging:B/bluez/standard/x86_64 [ 39s] checking systemd system unit dir... Package systemd was not found in the pkg-config search path. [ 39s] Perhaps you should add the directory containing `systemd.pc' [ 39s] to the PKG_CONFIG_PATH environment variable [ 39s] No package 'systemd' found [ 39s] configure: error: systemd system unit directory is required