kmod

Edit Package kmod
No description set
Refresh
Refresh
Source Files
Filename Size Changed
0001-testsuite-repair-read-of-uninitialized-memory.patch 0000001122 1.1 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 0000003400 3.32 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
_multibuild 0000000064 64 Bytes
kmod-30.tar.sign 0000000833 833 Bytes
kmod-30.tar.xz 0000567484 554 KB
kmod-testsuite.spec 0000003409 3.33 KB
kmod.changes 0000029541 28.8 KB
kmod.keyring 0000003455 3.37 KB
kmod.spec 0000005912 5.77 KB
no-stylesheet-download.patch 0000000395 395 Bytes
usr-lib-modprobe.patch 0000002797 2.73 KB
Revision 221 (latest revision is 240)
Jan Engelhardt's avatar Jan Engelhardt (jengelh) committed (revision 221)
bugnr
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