On Thu, Feb 26, 2004 at 08:20:39PM +0100, Carlos wrote: > [...] > > > No, I said something completely different, you didn't read anything I > > > wrote, did you? :) > > > > I did read it, but I mostly saw a lot of frustration in an area that I > > don't have a lot of familiarity with, and which is -- in the absence of > > standardization -- a matter of preference. > > > > > Anyway, forget about the issue. I see you don't have time to think > > > about it and would rather follow blindly a standard or upstream. > > > > If I don't have enough information about, or experience with, a subject > > to make an informed decision, then I don't make one. > > > > If I am going to break with a standard, or with upstream, I need a damn > > good reason. Frankly, you weren't offering one. You were just angry > > and impatient. (You appear to still be the latter.) > > I thought I was giving four good reasons :). The first one, about > rendering us_intl unable to produce a quotedbl maybe even merited a > serious bug by itself. I didn't gather that us_intl was unable to produce a quotedbl keysym; just that it wasn't able to produce one using the compose sequence you were accustomed to. > You don't seem to question upstream modifications to config files, but > seeing the CVS logs, I don't see them being too careful when commiting > changes. You had the bad luck of picking up the file between the > blunder and the correction :). I entirely agree with you here. Upstream is not always careful. I too, sometimes make mistakes I have to revert later. But I'm more responsible for my own bugs than upstream's. So, when I don't know what to do one way or the other, I trust my upstream. > See, I was angry and impatient because the changes to /etc/X11/xkb/* > broke my keyboard configuration. They changed rules/xfree86 and I > couldn't configure correctly the keyboard, until, after much struggle, > I learned to use the keycodes/types/symbol system and bypassed the > rules/layout/variant one. And then, when I finally managed to build a > good configuration, saw that <dead_diaresis> <space> was broken too... > :) Believe me, it is very easy for me to imagine how aggravating this was. Similar frustrations accompany efforts to use code written by people who have only been exposed to x86 machines on other platforms. :) > You don't want to break with standards or upstream, but what about > breaking with your users? Changes in configuration files, should, > IMHO, be carefully thought and justified... I think you will have a > lot of bug reports related to the keyboard as more people upgrade. Once you pointed out the upstream patch (and commit logs), you made a convincing case for backporting this change to Debian's XFree86 packages. > Ok, I'll try to be clear and cool when reporting further bugs :). > > Thanks for your explanatory response. Thanks for being patient with me, and providing more information when I asked for it. Some people file bugs in a state of rage and then refuse to communicate further. -- G. Branden Robinson | Debian GNU/Linux | // // // / / branden@debian.org | EI 'AANIIGOO 'AHOOT'E http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature