PSION'S OPENEMBEDDED BUILD TREE =============================== (This README.txt was added by the PsionLX release for navigation. It is NOT one of Psion's files. Everything else in this directory is theirs, and the tarball one level up -- netbook-linux-sources.tgz -- holds the unaltered original if you want to checksum against it.) 2,163 files. 263 recipes. Checked out by petern@psiondev.com, dated 26 April 2006, with the CVS metadata intact throughout. THIS IS THE AUTHORITATIVE STATEMENT OF WHAT PsionLX ACTUALLY WAS. If you want to know whether something is genuinely Psion's, this tree answers it. START WITH TWO FILES meta/soho-image.oe The image recipe. It names the finished artefact -- "soho-image", which is where the lost filename comes from -- and lists exactly what went into it, including the tweak that creates the lx user with uid 1000. meta/meta-psion.oe The application manifest: psion-apps, psion-net, psion-media, psion-games, psion-debug. Every application PsionLX shipped is named here. ALSO INSIDE Psion's own artwork -- the GTK and matchbox theme, application icons, the boot splash, window decorations. Their session scripts, dock layout, keyboard map, and the netBook-specific pcmcia, PPP and power configuration. And 82 patches against upstream applications, several of them substantial: abiword-psion.patch alone is 4,515 lines. WHAT CANNOT BE FETCHED BY ANYONE, EVER AGAIN Five recipes pull from ${PDCVS}, which is cvs://@cvs.psiondev.com/var/lib/cvs -- Psion's private CVS server. It no longer exists and was never archived: gpe-appmgr the launcher, the TODAY/PROGRAMS/TASKS strip and the Today screen (tag GPE_APPMGR_56) gpe-buttonbox the dock gpe-helpviewer infoprint psion-kernel This is why the launcher and dock in the rebuilt images are reconstructions rather than Psion's code, and why the icons Psion drew for them are lost. It also explains a long-standing puzzle about the community GPE image: it contains 43 gpe-* binaries but not those two, because whoever built it could not reach Psion's CVS either. HOW TO USE IT WHEN MODIFYING THE BUILD Read the relevant .oe recipe's do_install() to learn the exact target path and mode, then install Psion's file byte for byte. Do not hand-roll a substitute -- an invented config looks plausible and then becomes impossible to tell apart from a genuine bug.