On 3/2
Those who need it are messaging-ui, call-history, commhistory-daemon (handling the storage), qt-mobility, qt webruntime, at-phonebook, msgsync. I assumed the dependencies have been checked before announcing the change. Where is this task open and to whom? Is there a bug?
What are the other options instead of libcommhistory?
the libcommhistory package is not even in any of the images... how can you claim that it's actually this critical? Does the MeeGo dialer even use it? When I spoke with the owner of the dialer app (which is supposedly the key user of all this), this really did not come up as something that is currently in use and working... quite the opposite.
(it might work in your maemo OS, but that is of no consideration)
architecture decision, and as such, it must have addressed all the basic use cases and consequences _before_ it was made, right?
all the cases that we cared about were looked into, risk assessment was made and some detail investigation was scheduled for after the decision for some corner cases that were not deemed critical and where no good current solution was in place.
I cannot believe these important dependencies were not considered when the decision was made to move back to EDS... BTW who made the decision (meeting minutes please?), and where is it documented?
The MeeGo architecture team made these decisions in consultation with the various handset and tablet architects.
I know it's not popular with you and some other @nokia.com folks... but so be it.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
