Hello Richard, Sunday, July 9, 2006, 3:58:31 PM, you wrote:
> On Sun, 2006-07-09 at 13:47 +0200, Rene Wagner wrote: >> it makes me sad to see yet another message of this type by you. I was >> positive that by now everyone had "got over it" but now the bashing >> starts again :( > :-( > Having looked at it, there were valid concerns about bits of the patch > but Koen's email was also rather strongly worded :-/. In case you have time, I'd appreciate a hint what makes people say 'eerie' here - the patches were actually just duplicating existing bits for h4000 (ahem, that's how OE is setup now, this must be changing, sure), removing kernel version hardcoding from handhelds-pxa-2.6_cvs.bb (that's a must, and needed, or at least not doing so didn't work for me, even though I'm using BitBake 1.5). Oh, an killing a patch off handhelds-pxa-2.6_cvs.bb - that's mostly of lazyness. >> As for the other things you changed, well, we're not using a current >> version of bitbake (I outlined the reasons a while back) > I realise this is your choice and accept that. It does concern me though > as you're becoming stuck with what amounts to old buggy and unmaintained > software. Its a shame we've reached an impasse on the issue as one small > change allows you to use the latest bitbake. I agreed that change isn't > ideal but is it worth the cost? FWIW, the way OE uses that variable was > wrong and should never have been allowed, it just happened to work. We > need to find an alternative to what its doing, particularly with the way > bitbake development will head (multithreading). In the meantime, that > "fix" does avoid the problem in a way that is totally hameless and will > not break anything. Just in case, I'm using BitBake 1.5 SVN trunk from ~2weeks ago. The reason is obvious - from outsider's point of view, BB wasn't really usable until that nice caching was added. Oh, just to add more novice's rambling - I feel the same way now about Familiar's git repo vs OE' monotone - git is *so* nice, quick, and attentive. Does just what I want. And I yet have to figure how am I going to get diffs between consecutive revisions in monotone, if child rev may have two parents; who and why wrote viewmnt, if it just cannot do the trivial thing which is required from SCM viewer - show the file tree, allowing to see history for a file, and get diffs between arbitrary revisions of it; and why monotone's author, instead of doing nice unit testing before release, prefers to do "verification", which "may take some time" on my own machine in my own time. ;-) > I'm a little concerned that familiar is drifting away from OE the way it > is. I no longer see commits to familiar and I suspect familar devs don't > see commits to OE. > As an example, looking at the above patch, I see you've made some > improvements to tslib and this "detect-tsdevice" which I was unaware of > and would have been useful as I also found similar bugs in poky/OE and > fixed them a different way. OE now has udev handling the tsdevice setup. > We should really be trying to share these things. I also was surprised by that utility - it seems it does just what "detect-stylus --device" does. Perhaps compiled w/o X dependencies? As for udev handling - sounds very nice! That's what I also though of - why all that gore of hardcoding specific /dev/input/eventX (re: Opie), of all these utils stuffed in /etc/profile, if that's clearly a metter for udev to provide nice symlinks like /dev/input/touchscreen (as 'ts'a pparently in use) and /dev/input/keys (the latter is also important - again, opie doesn't work out of box say on h4000, because expecs keys on event0). >> > I've extracted the sensical portions, cleaned them up *a lot* and >> > committed them. >> >> ...and once again you failed to even mention the original authors. > People do need to acknowledge where patches come from and it is > important. Koen has been better at referencing poky recently which is > good so we're perhaps slowly getting somewhere here. I'm not entirely > sure how to take the o-hand reference in one of todays commit messages > so I'm choosing to ignore it. Commit messages aren't really for jokes > (I'm being charitable and taking it as one). > Richard -- Best regards, Paul mailto:[EMAIL PROTECTED] _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe
