Gerhard Brauer wrote: > i'm seeing that Anthony closed this bugreport. > I - as the reporter - don't agree.
I reopened it yesterday, didn't i? > Using m-a is *solution* to go round the problem. I think so. > Short info how i notice the problem with this package: > On mailing list debian-user-german one ask to compile the modules on an > seperate pc, rans in problemes and ask on the list. > I told him to read the Readme's and go the way proposed there with > dpkg-reconfigure or debian/rules binary-modules. He still has problems. > Then i do it on my pc and found the problems reported by my two reports. > > So i think we must: > Find a solution doing it right like the Readme's say. And > dpkg-reconfigure <paket> is a "official" debian tool. BTW: > dpkg-reconfigure is the only paket-tool to configure > /etc/lirc/lirc.conf. And the debconf stuff is really broken here, I gree. But Sgran is working on changing it completely. > Or we must change the Readme's to force users to use m-a. But how > could one read them when the paket unpacked? Just depend on m-a and recommend it in the README.Debian, which, BTW, should be completely rewritten ;) > I would prefer a fix like: > Using dpkg-reconfigure to edit the lirc.conf. Then, instead of > building the modules, debconf dialog suggest the user to install m-a > und use this to build the modules for his kernel. To document this i > prefer to put a Readme.Debian in the paket where this is also > documented. We are also considering just releasing a deb with prebuilt modules for debian kernels, as ipw2100 is doing, for example. -- ยท''`. If I can't dance to it, it's not my revolution : :' : -- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com
