Nasa <[email protected]> wrote:
allow interested parties to get a fully bootable system and then add
drivers/UX via zypper as thier hardware requirements demand.
Agree: what was annoying me this week was ruining a working set of drivers
by zypp-updating from IVI repositories. My whiny complaint is not about
lack of driver support for my hardware, which I *had* working, but the fact
that my /usr/lib was overwritten by drivers for a different Atom processor
when I updated.
Having said that, in an ideal world we'd have specific repos for IVI for
widely used and relevant HW platforms. This week I've been trying to
build a liveusb IVI image for ExoPC using mic2 and a mix of packages from
1.2.0.90, 1.1.99 and Arfoll's own special brew. The set of packages is
one that I have actually working on the hardware, where I have patched their
dependencies up with a script, but mic2 knows I'm cheating and fails with
messages like, "meego-ux-daemon requires libGLESv2.so.2" and "libqtgui4
requires libEGL.so.1". In fact the set of packages contains those
libraries, but not where mic2 has been told to look for them. I guess I
need to figure out how to rebuild the packages whose dependencies are
failing against the libraries I'm actually using or even better, so that no
assumption is made, as described in previous paragraph.
--
Alison Chaiken
(650) 279-5600 (cell)
http://www.exerciseforthereader.org/
"What you do for a living is not be creative, what you do is ship." -- Seth
Godin, vimeo.com/27067169
_______________________________________________
MeeGo-ivi mailing list
[email protected]
http://lists.meego.com/listinfo/meego-ivi
