On Mon, Nov 02, 2009 at 01:11:28PM -0600, Mario Limonciello wrote:
> It should be worthwhile to note that there is an upstream "common"
> postinst that is available with DKMS 2.1.0 and later. It would be most
Yes, /usr/lib/dkms/common.postinst. I hadn't thought about the version
dependency, though -- thanks for reminding me. (That's another thing
that dh_dkms would get right.)
BTW, I couldn't help but notice that the postinst you wrote for
virtualbox-ose calls dkms directly. Was that intentional?
> Here's how it's normally used in the DKMS mkdeb template:
Thanks! I really should take a closer look at the mkdeb rule.
I'm not sure I understand the $ARCH test, though. Why does this generic
postinst arbitrarily decide which arches are supported by a module?
Also, could somebody comment on what a prerm should look like? From
what I understand, it should be something like:
dkms remove -m $NAME -v $CVERSION --all || true
(virtualbox-ose redirects stdout but not stderr, openafs does neither.)
This should be run on remove/upgrade, at least, and possibly deconfigure
as well, I'm not sure. virtualbox-ose also does it on purge, which I
believe is redundant, if not wrong (dkms may not be installed at that
point).
--
I was attacked by dselect as a small child and have since avoided
debian.
-- Andrew Morton
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
