File not found: kmod-testsuite.changes

kmod

Edit Package kmod
No description set
Refresh
Refresh
Source Files
Filename Size Changed
0001-testsuite-fix-path-for-test-user.patch 0000001071 1.05 KB
0002-modprobe-Recognize-allow-unsupported-modules-on-comm.patch 0000001138 1.11 KB
0003-libkmod-config-Recognize-allow_unsupported_modules-i.patch 0000000928 928 Bytes
0009-libkmod-Implement-filtering-of-unsupported-modules-o.patch 0000003334 3.26 KB
0010-modprobe-Implement-allow-unsupported-modules.patch 0000003279 3.2 KB
0011-Do-not-filter-unsupported-modules-when-running-a-van.patch 0000001510 1.47 KB
0012-modprobe-print-unsupported-status.patch 0000002423 2.37 KB
README.usrmerge 0000000386 386 Bytes
_multibuild 0000000064 64 Bytes
_scmsync.obsinfo 0000000151 151 Bytes
build.specials.obscpio 0000000256 256 Bytes
kmod-33.tar.sign 0000000833 833 Bytes
kmod-33.tar.xz 0000514428 502 KB
kmod-testsuite.spec 0000003391 3.31 KB
kmod.changes 0000032403 31.6 KB
kmod.keyring 0000003455 3.37 KB
kmod.spec 0000006008 5.87 KB
Latest Revision
unknown committed (revision 240)
[info=c0d997b9f87fef11b441dffd32addda660379ac46be324866950df1bb120bbfb]
Comments 2

Luciano Santos's avatar

Why are we using /usr/include/kmod/? The standard location across the major distros is /usr/include/. Only openSUSE and NixOS (that I know so far) use a subdirectory under the include directory to place its header files. I just had to patch an app because of that, now I don't even know if a change upstream to maybe use a var to store the libkmod.h location will be accepted.


Jan Engelhardt's avatar

To flag all apps that fail to use pkg-config to discover the paths.

openSUSE Build Service is sponsored by