DKMS package for dahdi-linux

[Tzafrir Cohen]

On Tue, Aug 25, 2009 at 01:29:26PM -0400, Jean-Michel Dault wrote:
> On Tue, 2009-08-25 at 13:10 -0400, Jean-Michel Dault wrote:
> > > 1. the .install file installs files into /usr/src/dahdi-linux-2.2.0.2 .
> > > Is the specific version number of DAHDI required? Generally newer
> > > versions of DAHDI are expected to be upgrades. Or are you interested in
> > > installing several versions of DAHDI alongside on the same system? I see
> > > several technical issues with that.
> > All dkms packages seem to be built this way. I think dkms has its own
> > versioning system. I'll dig further.
> 
> OK, from: http://linux.dell.com/dkms/manpage.html
> 
> "add
>         Adds a module/version combination to the tree for builds and
>         installs. Requires source in /usr/src/<module>-<module-version>/
>         as well as a properly formatted dkms.conf file."

I'm not happy with this one. We will now have two copies of the dahdi
source tree (three, if you count the actual .orig tarball).

Having the full version is really pointless. I believe it also pollutes
the /usr/src namespace.

Specifically for DAHDI, it will create unexpected pathes on the
installed system. Upgrading from 2.2.0 to 2.2.0.2 (a minor upgrade) will
change pathes. Also note that those cannot be installed alongside for
other reasons.

>         
> "build
>         Builds the specified module/version combo for the specified
>         kernel. If no kernel is specified it builds for the currently
>         running kernel. All builds occur in the
>         directory /var/dkms/<module>/<module-version>/build/."
> 
> So, yes, the module version has to be specified. For package maintenance
> however, there must be a way using rules or dpatch to auto-generate that
> version from the debian tags...
> 
> > > 2. Shouldn't dkms.conf be a generated file? Is there any reason it
> > > should exist before the build? Why does it need to include the name of
> > > each and every module?
> > Again, all dkms packages seem to be build this way. 
> > I'll do a search and post more info later. 
> 
> "When performing an add , a proper dkms.conf file must be found. A
> properly formatted conf file is essential for communicating to dkms how
> and where the module should be installed."
> 
> So, yes, every module must be defined in dkms.conf before the build,
> because dkms builds in a special directory and doesn't execute "make
> install".

It will require maintinance. What happens if a module gets built but is
not mentioned in the config file?

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir