For rdma-core binary package, the dependency is really on systemd-udev
which provides udevadm. Since systemd can be installed without udev,
the dependency was not effective. But actually the dependency is not
needed at all, because the system will behave the same with and
without it. (If systemd-udev is installed later in the transaction,
the call to udevadm trigger is not necessary. If systemd-udev is
installed earlier in the transaction, the call to udevadm trigger will
succeed. And if if systemd-udev is not installed at all, it means that
there's no hardware support and udevadm doesn't need to be executed at
all.)
Similarly, %{systemd_requires} is not necessary for the systemd unit
scriptlets. See https://pagure.io/packaging-committee/c/46010f8b6ab077bf.
That commit also has a long explanation.
Also co-own the directory to avoid unowned directory warning.
On architectures without coherent DMA semantics, rdma-core automatically
turns off those providers that have a hard requirement on coherent PCI
DMA. We need to conditionalize our files and such to compensate for the
missing files.
Signed-off-by: Doug Ledford <dledford@redhat.com>
We aren't building for the old SysV initscripts package any more, so
drop the ifup-ib/ifdown-ib scripts that only work when the initscripts
package is installed. This keeps us in line with changes going into the
rdma-core-17 package release.
Signed-off-by: Doug Ledford <dledford@redhat.com>
Major spec changes to accommodate the update from 14 to 16.2.
Many of the rdma-core provided services are not done via udev on demand
loading.
Configuration file layout has changed.
Signed-off-by: Doug Ledford <dledford@redhat.com>
