Hey Stefan:<br><br><div class="gmail_quote">On Fri, Aug 7, 2009 at 15:12, Stefan Lippers-Hollmann <span dir="ltr"><<a href="mailto:s.L-H@gmx.de">s.L-H@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi<br>
<div class="im"><br></div>
As it seems this patch does mostly 2 things:<br>
- nuking debconf for lirc-modules-source<br>
this is something I very much agree about<br>
- switching the module buildsystem to dkms<br>
well, dkms has been uploaded to unstable recently and the first modules<br>
are switching over (drbd8-source and optionally openafs-modules-dkms)...<br>
So far I haven't seen a canonical recommendation other than<br>
module-assistant for packaging kernel modules in Debian and given that<br>
the intention is to add lirc-modules-source to linux-modules-extra-2.6,<br>
this switch would be detrimental to that goal (which also requires to<br>
rename lirc-module-source to lirc-source for technical reasons).<br>
This needs further discussion with the other pkg-lirc team members, but<br>
the most I might see here, would be an option like openafs-modules-dkms,<br>
which offers both ways in separate binary source packages.</blockquote><div>What some packages have been doing is doing a DKMS option or the pre-included modules side by side. I think this is a good compromise. In Ubuntu we only use the DKMS solution if the user is running their own custom kernel or needs to patch the modules themselves and needs a good means to do so. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
(on a very personal side note, I do not consider dkms a viable method to<br>
ship kernel modules in Debian, as dpkg knows nothing about it, the<br>
actually built modules are not transferable and, even worse, dkms builds<br>
as root without ever asking the user about it. I for one was pretty angry<br>
to get surprised by drbd8-source suddenly starting to compile on my<br>
system, while I'm very cautious not to risk its integrity by doing<br>
"unsafe" procedures as root - and there've been enough stories of bad<br>
Makefiles replacing /dev/null with a regular file and similar unwanted<br>
side effects. That said, dkms' biggest assets of semi-automatically<br>
adapting to new kernels could be trivially ported to plain<br>
module-assistant:<br>
- Vcs-Svn: svn://<a href="http://svn.berlios.de/fullstory/dmakms/trunk" target="_blank">svn.berlios.de/fullstory/dmakms/trunk</a><br>
- Vcs-Browser: <a href="http://svn.berlios.de/wsvn/fullstory/dmakms/trunk/" target="_blank">http://svn.berlios.de/wsvn/fullstory/dmakms/trunk/</a><br>
- <a href="http://lists.debian.org/debian-devel/2008/10/msg00876.html" target="_blank">http://lists.debian.org/debian-devel/2008/10/msg00876.html</a><br>
but again, this is my very personal opinion)</blockquote><div><br>I took note of this and wrote a patch for DKMS to not build as root when possible: <a href="http://linux.dell.com/git/?p=dkms.git;a=commit;h=e2a638e6dca5c12db680cbcea1aff55298decbf4">http://linux.dell.com/git/?p=dkms.git;a=commit;h=e2a638e6dca5c12db680cbcea1aff55298decbf4</a><br>
<br>It is conditional, as on RHEL and F11 it appears that this doesn't work. It works properly for Ubuntu (and I'd expect Debian too).<br><br>Including the module in the packaging system is a more complex problem. I'd too like to solve that, but that discussion should be raised on dkms-devel@ Dell ML or the dkms Debian mailing list. I'm on both, and open to ideas. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Once we have a hal aware lirc version in svn, this is likely to be<br>
relatively easy to accomplish. DKMS might be a little problem, but can<br>
probably be worked around in the packaging.<br></blockquote></div>I've got a few more patches to submit, but I'm waiting to see how many more of these can get directly upstream first.<br clear="all"><br>-- <br>Mario Limonciello<br>
<a href="mailto:superm1@gmail.com">superm1@gmail.com</a><br>