Comment 9 for bug 238864

Hi,

I've integrated support for mkdeb without dkms add into the dkms script
itself.

The mechanism is simple: -m and -v are required for most (all)
operations, and not supplying -m and -v didn't previously have any
meaning and was an error.

Now, if -m and -v are not supplied, then it is taken that you are in a
working copy of your DKMS source tree - for example if you manage this
using git or hg.

It is assumed that dkms.conf exists in the current directory and defines
the name and version of the module.

So now you can run, for example, "dkms mkdeb --source-only" from the
root of this working copy and you'll end up with a .deb in the parent
directory.

This should not break any existing functionality as the new mode of
operation only takes place if -m and -v aren't specified, which
previously was an error.

Robie.