QUOTE(koen @ Mar 22 2006, 10:04 PM)
QUOTE(Armagon @ Mar 22 2006, 09:37 PM)
I'm looking for a handy script that'll take a pdaXrom executable, and tell me what the package dependancies are (so that I can put that in the ipk control file.) Does anyone have such a beast?
I assume that it'd have to use the output of ldd on the Zaurus, or the output of
armv5tel-cacko-linux-objdump -x executable_filename | grep NEEDED
when you cross-compile. I also presume that it'd need to use (possibly several) Filelist files, from the feeds that contain the dependancies.
So, again, does anyone have such a script, or a similar solution? (Barring that, would anyone write such a script?)
In theory. In practice firefox won't install on OZ on my freshly flashed 6000l using the simple command"ipkg -d sd install firefox" It downloads firefox,whips up a bunch dependencies, decides it should install thunderbird, can't find thunderbird, and stops. I didn't request thunderbird there, and firefox isn't dependant on thunderbird. I would view this as indicative of a not-quite-stable-at-best solution for managing dependecies.
I hate to say stuff like this. I really do. gpe 2.7 is gorgeous, the minibrowser is cool, even if a lot of sites crash it, and the work that went into OZ and openembedded, the idea of a unified handheld OS, is to be commended.
On the other hand OZ guys posting OZ or OE propaganda in pdaXrom threads is really not too cool. Especially when their stuff still doesn't seem to work as well as pdaXrom. proof: If I type "ipkg -d sd install firefox" on pdaxrom on my 6000 I get firefox working on my 6000. If I do it in OZ/GPE I get a failed attempt to install Thunderbird.
Which do you think constitutes a better fit to any reasonable definition of "working?"
I realize Armegon was talking about ipkg generation, not installation, but wasn't it OE that generated the firefox ipkg that thinks it needs thunderbird?
Firefox is not some bit of useless exotica. If I want to access any of my work sites, or do online banking, the gpe browser won't do it. It is a pretty standard piece of software with widely known dependencies that should NOT be a problem to install.
I'm not trying to flame here. I really think OZ has improved. But let's not kid ourselves. OE is not (yet at least) the solution the dev team would like it to be. Maybe it is a case of too much familiarity (no pun intended). To someone working on OE and with OZ constantly, misbehaviours of the sort I cited must look pretty trivial.
But to me, at least, this pushing OE stuff is kinda like the guy at the office who forces everybody to look at baby pictures. you know?