One thing that did not happen prior to the change in QMF package AFAIK is to alert maintainers of packages/apps that list QMF as a dependency.
I am now chasing a SMS bug that did not exist with the libaccounts/sso version of QMF (don't have thw bug # at the moment). Caught me by surprise. [Sent from my phone] ----- Original Message ----- From: Arjan van de Ven [mailto:[email protected]] Sent: Saturday, March 26, 2011 01:00 PM To: [email protected] <[email protected]> Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: [MeeGo-dev] [meego-packaging] [meego-commits] 15232 accepted: Trunk:Testing/qmf On 3/25/2011 2:28 PM, [email protected] wrote: > Moving the thread to meego-dev. > > I looked deeper into this QMF promotion. Until now,we (MeeGo) used a modified > version that includes libaccount/libsignon integration. this was done properly as the upstream tarbal + patch, right? (if not, this is very obviously an improvement, to at least not use a contaminated tarbal) > Since the SR#15232, we're using the upstream QMF version and by extension, > dropped the integration. > > My questions: > 1. Is it an architecture team decision? the architecture team normally doesn't pick versions/etc.... not using libaccount/libsignon would be in the real of the architecture team obviously. will get back on that. > 2. Why use an older QMF upstream version? (and introduce epoch) using the latest upstream version would be totally fair game. As to the why the package went away from a contaminated frankenthing to a clean upstream one... that not only sounds like a good idea, it actually is. there were many issues with the frankenpackage, while the upstream one, which is very much better maintained, fixes lots of these. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
