Quote:
|
Quote:
Quote:
Quote:
Quote:
Code:
rm -rf /lib/modules/*/location/to/modules.ko |
Quote:
Code:
\removepkg |
Quote:
|
@bassmadrigal: Thanks again for the suggestion and example how dkms can be directed to build kernel modules into the package. I adapted my Slackbuild to have this as an option. It's very nice to see quickly what dkms does (provided the script covers/reproduces all its steps). With this in mind, the package can work without a douninst,sh. Another thing, though, is that one needs to be aware to call dkms to remove modules from a running kernel (after an upgrade) BEFORE removepkg. As it needs a dkms.conf file for this (see above).
A way around this is to place a copy of the dkms.conf somewhere outwith the files and folders controlled by pkgtools. This can be done from the doinst.sh by means of a simple copy command. Then, a douninst.sh can a) first call dkms with this 'parked' conf (put in /etc/dkms) for guidance what driver to uninstall and -after completion - b) can remove the conf-copy from /etc/dkms. This works quite nicely, but means appreciation of a douninst.sh. Which defies the rationale not to call dkms during installation of the driver. So, as the default option, the Slackbuild is set to make full use of dkms by means of the doinsth.sh and a douninst.sh. And by doing so may better reflect what the developers of the drivers have in mind (they advice to use dkms for installation of their drivers). You can check it here: digimend-drivers-dkms cheers |
Quote:
doinst.sh: Code:
VER=@MODULE_VERSION@ Code:
VER=@MODULE_VERSION@ |
All times are GMT -5. The time now is 02:31 PM. |