[meego-packaging] [meego-commits] 15232 accepted: Trunk:Testing/qmf

[Arjan van de Ven]

On 3/25/2011 2:28 PM, fathi.boudra at nokia.com 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.