On Tue, Sep 20, 2005 at 06:52:23AM -0400, Andres Salomon wrote: > On Thu, Sep 08, 2005 at 01:23:30AM -0400, Andres Salomon wrote: > [...] > > I'm rather disappointed by the lack of responses to this. I don't intend > to do any more infrastructure work on the kernel packages until we pick > something; I don't particularly feel like having the things I write > rewritten multiple times, nor do I want to bother rewriting other people's > stuff. >
Hm, for some reason muttng [1] doesn't show waldi's response. Anyways, to follow up: > > I'm comfortable with > > either ruby or python; I suppose it depends on what others are more > > comfortable with. > I don't know anything about ruby. Well, others are going to have to learn as well. As I said, I don't care which is chosen, but I'd like to get others input as well. The only person I'm aware of on the kernel team that already knows ruby is joshk; I know you and Jurij know python already. I want to hear what other people prefer as well, but I haven't heard many responses. If it turns out that no one else knows ruby or python (or has a preference of what they want to learn), I'll pick python.. > > Once we have a common language, we can have a common > > library as well > linux-2.6/debian/lib/python already exists. Right, which is fairly new, and assumes everyone knows python. > > (ages ago, I wrote half a Kconfig parser in racc; > I have a fullblown parser which is derived from the original yacc and > flex files written in python. Is it functional? I remember seeing you working on it on IRC, but were having problems; does this mean you finished it? [1] why must all nntp readers (and mail clients) suck? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
