[Pkg-fglrx-devel] r776 - fglrx-driver/trunk/debian

Michael Gilbert michael.s.gilbert at gmail.com
Mon Sep 5 16:22:34 UTC 2011


On Mon, 5 Sep 2011 12:20:52 -0400 Michael Gilbert wrote:

> On Mon, 05 Sep 2011 09:41:37 +0200 Andreas Beckmann wrote:
> 
> > On 2011-09-04 19:28, Michael Gilbert wrote:
> > > I think we only want to support dkms.  What does providing this gain us?
> > > Is it needed for multiarch for some reason, and if so, why is dkms
> > > insufficient?
> > 
> > dkms is not yet the ultimate solution for kernel modules. It's fine for
> > desktop users with a single machine ... but I prefer to deploy locally
> > prebuilt module packages instead of having servers compile them. And I
> > take the responsibility for making an updated module available in case
> > of kernel updates.
> > I haven't tried the .deb building capabilities of dkms, but according to
> > the BTS it's not doing what people expect. (And how can I do this
> > without changing the running kernel module of the build machine? All
> > *-dkms packages depend on dkms and build and install the module in their
> > postinst)
> 
> This perphaps isn't ideal, but you can install the -dkms package with the
> linux-headers packages not installed, which will result in no automatic
> module installations.
> 
> If there are bugs with dkms's mkdeb, then let's identify what they really
> are and get them fixed.  From my perspective, people just haven't understood
> how to use it, and have just wanted to complain.  There aren't any real dkms
> bugs with respect to mkdeb to fix right now [0].

Oops, there is http://bugs.debian.org/554843, which I can look at some time.

Mike



More information about the Pkg-fglrx-devel mailing list