last time I checked all the patches were on externe.net/zaurus/kernel , I think.
The binaries got posted in /flash/..... and there were separate parallel dirs with source and patches.
If the current set isn't up yet, I am assuming it will be. Have a look.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79937\"][{POST_SNAPBACK}][/a][/div]
I'm not worried about that. A lag between current binaries and posted source is a technical violation of the GPL, but I assume it's all in good faith, particularly if it doesn't go on too long.
Using a public VC system gets you out of trouble there, of course.
I think the troll was about opera, etc in the Qtpalmtop.rom not having source posted. I take that to be more of a fair use issue, as it doesn't pretend to be anyting but sharprom on a nand resize, and anyone with a 6k is entitled to use sharprom. afaik the patches that are actual new guylhm rom stuff get posted.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79937\"][{POST_SNAPBACK}][/a][/div]
Well, that's interesting. Has he patched the Opera binary to use his keymap? I assume so. The legal and ethical questions you can argue about, but the practical problem is that we will all have to rely on Guylhem to do the patching for subsequent releases, or else do it ourselves with varying results. And if a new binary app comes out that allows for, say, immediate attraction of selected members of the appropriate gender, then we'll have to.. well, we probably wouldn't have to wait long for him to patch the keymap on
that app. But you get the idea.
That approach will not scale. It is guaranteed to make this project a backwater in the (already small) Zaurus community.
The custom keymap is far more trouble than the problem it's designed to solve, IMHO.