Arch Linux User Repository

Pleas use a hook, dkms now have a hook to trigger dkms buildings at install, so the dkms building in the install file is unnedded now and just trigger the dkms building twice.

Reported out of date. Calculated sums not correct anymore and patching fails.

Have put the PKGBUILD and the install file in a pastebin for better readability: http://pastebin.archlinux.fr/1730692 http://pastebin.archlinux.fr/1730693

Improved PKGBUILD: _pkgname=tp_smapi pkgname=${_pkgname}-dkms pkgver=0.41 pkgrel=7 pkgdesc="DKMS controlled modules for ThinkPad's SMAPI functionality" arch=(any) url="http://www.thinkwiki.org/wiki/Tp_smapi" license=('GPL') depends=('dkms') conflicts=('tp_smapi') provides=("tp_smapi=${pkgver%.*}") options=(!strip) install='tp_smapi-dkms.install' source=("https://github.com/x539/tp_smapi/archive/tp-smapi/${pkgver}.tar.gz" 'dkms.conf' 'kbase.patch') sha256sums=('7b7008c2d1cb0849d51fc9791b23dd1f36cf80c899fd4d802878f56abf87516a' '4d2a4804fbacd606d4d9c4f7ab307fa1522d35e021c58ac565ec895483ef4f75' 'b0e53ad7192c9b01bd0897128a1b2453bc28685ad1bd365477eac472065d9d89') prepare() { # patch Makefile for recent kernel module directory change cd "${srcdir}/${_pkgname}-${_pkgname/_/-}-${pkgver}/" patch -p2 < ${srcdir}/kbase.patch sed -i 's/KVER/KERNELRELEASE/g' Makefile } package() { cd "${srcdir}/${_pkgname}-${_pkgname/_/-}-${pkgver}/" mkdir -p "${pkgdir}/usr/src/${_pkgname}-${pkgver}" cp -a {*.{h,c},Makefile} "${pkgdir}/usr/src/${_pkgname}-${pkgver}" cp ${srcdir}/dkms.conf "${pkgdir}/usr/src/${_pkgname}-${pkgver}" } In the dkms.conf set: PACKAGE_NAME="tp_smapi" And in the install file remove all the -dkms suffixes: ver=0.41 post_install() { DKMS=`which dkms 2>/dev/null` echo ">>> DKMS: Module add, build, and install " $DKMS add -m tp_smapi -v $ver for kver in /usr/lib/modules/* do if test -e ${kver}/build then kver="`basename $kver`" $DKMS build -m tp_smapi -v $ver -k $kver $DKMS install -m tp_smapi -v $ver -k $kver echo ">>> Updating kernel modules..." depmod -a $kver fi done } pre_upgrade() { pre_remove } post_upgrade() { post_install } pre_remove() { DKMS=`which dkms 2>/dev/null` echo ">>> DKMS: Module uninstall " line=`$DKMS status -m tp_smapi` if echo "$line" | grep -E 'added|built|installed'; then version=`echo "$line" | sed "s/tp_smapi,\([^,]*\)[,:].*/\1/;t;d"` $DKMS remove -m tp_smapi -v $version --all fi } post_remove() { /sbin/depmod -a } Actually, the install file needs some more work to do: Since you are receiving the module version as a parameter, the first line (ver=) can be omitted.

tp_smapi-ck is a static package. The module is built during makepkg and that's it. This package ships the complete source of the module and some instructions for dkms to build it. That's why this package works with every kernel and why I won't add a specific kernels headers as deps.

I understand. I didn't know that this package is also meant for -ck users. I expected them to use tp_smapi-ck.

> Doesn't everyone use the linux package as it provides the kernel? Nope, for example if someone (like me) has only linux-ck{,-headers} installed, there's no linux{,-headers} present on the system.

@TamCore Thanks for your comment. > even if they don't use the linux package Doesn't everyone use the linux package as it provides the kernel? How can it be an optional dependency only if it was required to have it installed in order to install this package?

No, sorry. This would would require everyone to install linux-headers, even if they don't use the linux package. Also linux-headers is already listed as an optional dependency for dkms.