Hi, On 03/26/2011 10:00 PM, Arjan van de Ven wrote: > On 3/25/2011 2:28 PM, [email protected] wrote: >> 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)
I know that MeeGo QMF has its own repository in gitorious ([0]), but then I don't know how the packaging works (adding Vitaly in CC). > not using libaccount/libsignon would be in the real of the architecture > team obviously. > will get back on that. Hopefully you'll come back with some proposal/discussion, and not a decision? >> 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. The only one I'm aware of is BMC#11361. The biggest problem I can see with these Nokia-maintained packages (MeeGo QMF, Accounts&SSO and probably others) is that their development teams are mainly active on the Nokia product-driven developments, and very little time is allocated for the public MeeGo packages. Luckily, at least for Accounts&SSO, this is going to change starting from tomorrow. :-) Ciao, Alberto -- http://blog.mardy.it <- geek in un lingua international! _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
