Greg Cymbalski d28b0fd63e Optionally generate per-kver pinned kmod packages ...

Allow building the kmod pinned to an exact kver by defining
%{per_kver}=1 at build time:
- Package names use conventions used elsewhere in RHEL to indicate the
  kernel version built against
- A virtual package, kmod-scoutfs, preserves the existing name and also
  makes it simple to install with yum via repository
- Strict requirements on the kver built against in accordance with
  conventions
- Disabling automatic use of weak-modules

If not defining per_kver to 1, legacy behavior is preserved, meaning we
can deliver packages for the same scoutfs commit in both styles
depending on customer needs.

Signed-off-by: Greg Cymbalski <greg.cymbalski@versity.com>

2026-05-07 14:34:05 -07:00

..

src

Merge pull request #308 from versity/auke/totl-delta-repair

2026-05-05 13:05:57 -07:00

.gitignore

scoutfs: update rpm building infrastructure

2018-09-14 15:07:10 -07:00

Makefile

Require sparse, and filter kernel sparse output

2025-10-03 09:35:36 -07:00

scoutfs-kmod.spec.in

Optionally generate per-kver pinned kmod packages

2026-05-07 14:34:05 -07:00