Touche. You know, you could have just said, "Shut up, Phil." and saved yourself some typing.
I'll try the diplomatic way. Please can someone explain why hwdetect has been hardcoded into the Arch initscripts rather than provided separately as most similar tools are. Can someone also explain why this does not violate the KISS philosophy on which Arch is based and many of us have come to rely on. How's that? Better? Phil Judd Vinet wrote: >Dear Customer, > >Thank you for your kind words and suggestions. We are obligated to >fulfill your every need, and will dutifully change our course to match >your expectations. Your tireless constructive criticism is a greater >boon to this project than anyone else, and we will continue to strive >towards your benevolent and well-delivered expectations. > >Given your current record for diplomacy and public relations, we will >continue to take your suggestions with the highest regard. It's only >fair, seeing as you take the time to write to us whenever something >doesn't agree with you, and you are very adept at wording things in just >such a way that we immediately have an urge to move your requests to the >top of the pile. > >Our volunteers apoligize profusely for any problems or annoyances you >may have been caused when using this entirely free product. Once again >we have failed you, and as such, will issue a refund as soon as humanly >possible. > > >Sincerely, > >The Management. > > >On Sun, Nov 27, 2005 at 09:45:13PM +0000, Philip Dillon-Thiselton wrote: > > >>Why the hell does hwdetect have to be in the initscripts pkg if it is >>going to need so many updates? Generally I am pretty understanding of >>the devs and their odd whims but this one takes the biscuit. I could >>not give two shits about hwdetect and certainly don't want it on my >>system if I don't need it and I certainly don't want to have to mess >>about with the inevitable .pacnew files everyday just because hwdetect >>is being updated. Aside from all that it's a PITA for me and the >>gensplah initscripts - I have to update the whole pkg when hwdetect gets >>fixed and that should be handled entirely separately. Why on earth >>can't hwdetect run using a daemon like hotplug rather than having it >>hardcoded and then be totally optional. Quite frankly I'm amazed. >> >>I guess it would be less annoying if hwdetect wasn't a) so buggy b) >>reinventing the wheel and c) anti the Arch ethos. >> >>Sort it out, please. >> >>Phil >> >>_______________________________________________ >>arch mailing list >>[email protected] >>http://www.archlinux.org/mailman/listinfo/arch >> >> > >_______________________________________________ >arch mailing list >[email protected] >http://www.archlinux.org/mailman/listinfo/arch > > > > _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
