So, there's no explicit rpm dependency on AMB-- That's understandable in light of the fact that what's actually attached to Dbus or AMB is configurable.
That said, how does one know what must be configured for the javascript objects to 1. Be callable without error 2. Actually work correctly (assuming that the javascript does something even if lower level components are missing or misconfigured.) Thanks! Paul Paul Hanchett ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected] ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070 On Wed, Nov 13, 2013 at 9:42 PM, Ylinen, Mikko <[email protected]>wrote: > Hi, > > On Wed, Nov 13, 2013 at 10:04 PM, Gerken, Stephen < > [email protected]> wrote: > >> which provide the interfaces supporting tizen.mediaserver, tizen.speech, >> and tizen.vehicle respectively. (This is the simpler example; >> wrt-plugins-tizen has a much longer list of libraries, some of which >> support the rest of the namespace.) So far so good, but this is where I get >> stuck. I do not know what commands to give rpm in order for it to tell me >> what underlying packages are used by, for example, >> libwrt-plugins-tizen-vehicle-impl.so. I think it relies on the various >> automotive-message-broker rpms, but I am unable to find an rpm command >> which will tell me that tizen.vehicle is in any way reliant on AMB. Is rpm >> able to do this? What rpm command should I be using? >> > > I explained this in my previous email but I guess I wasn't clear. > libwrt-plugins-tizen-vehicle-impl.so talks to automotive-message-broker > over Dbus so there's no RPM dependency between the two. It can easily be > added to wrt-plugins-ivi using Requires: automotive-message-broker in the > .spec file. > > It's debatable whether D-bus dependencies are valid as RPM dependencies. > For the sake of architecture, it might be a good thing but I'm sure it's a > big no to many as well. > > There are other device web plugins as well that talk to middleware > services over dbus. Some implementations talk to capi-* libs which further > talk to the services. Remember to check those dependencies as well. > > -- Mikko >
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
