v3.2.0 - New functionality
Force rebuild of dependent modules
Force the rebuild of modules when BUILD_DEPENDS_REBUILD is set and modules declared in BUILD_DEPENDS change.
When a module is updated, all modules that depend on it need to be automatically rebuilt in the correct order. This is all gated throughBUILD_DEPENDS_REBUILD, which should be set on a per installation basis, for example:
$ cat /etc/dkms/<module1>.conf
BUILD_DEPENDS=<module2>
BUILD_DEPENDS_REBUILD=yes
Whenever <module1> is built and BUILD_DEPENDS is set, the version of the dependent module is saved in:
/var/lib/dkms/<module1>/<kernel_version>-<arch>/.dep_<module2>
Add post transaction command that can be specified per site / installation
Add a generic command that gets executed at the end of "install/uninstall" phases for modules. The post_transaction is configured in /etc/dkms/framework.conf and if set to any non-null value the command in there is executed with the kernel version that is the target of the command as the first parameter.
This can be set on a per-site or by distribution packagers of DKMS.
It's executed only at the end of commands that change the content of the kernel modules folder; so an install, autoinstall and remove|unbuild|uninstall command. When the directive is not set (the default) there is no behavior change for DKMS.
The action generates a log in the DKMS working directory using the facilities already provided by DKMS.
What's Changed
- Update man pages by @scaronni in #517
- Add logic for rebuilding modules when dependencies change by @scaronni in #515
- Add helper function for boolean variables syntax checking by @scaronni in #520
- Update tests by @scaronni in #523
- Do not use $ for describing framework.conf directives in the man page by @scaronni in #524
- Add post_transaction command by @scaronni in #522
Full Changelog: v3.1.8...v3.2.0
