Hi Peter, > > > You are correct about compat packages, using compat for the old > > > telepathy-qt4 was all wrong to start with, it was added to provide > an > > > old API to develop against, not something to run against, the real > > > reason why you would want a compat package. > > > > > > The applications listed below: libmeegochat/meego-handset- > > > chat/meegotouchcp-chat all require that old version to build, maybe > > > because they are broken. > > > > > > to summarise: You should verify that your change does not break > > > anything, in this case it does, but that is because the other > package > > > are broken and not using the new APIs. > > > Solution: > > > - We really do not need this compat package I think > > > - We need to fix those packages requiring the old API or if they > are > > > not maintained, drop them. > > > > Precisely, thank you. > > As telepathy-qt4 0.5 had been put into the distribution more than two > months > > ago, and the decision to push it was apparently agreed with the > architects > > (https://bugs.meego.com/show_bug.cgi?id=11358#c6), I assumed that > this is > > the only development API that needs to stay. > > Building of the client packages in the OBS projects has been blocked > by the > > presence of two pkgconfig(TelepathyQt4) dependency targets, now it > may be > > the time to check if they have been ported. > > > You cced right person, Baris, who can tell you a long story why meego > has such compatible 0.4.X of telepath-qt4. The requirement are from > Baris and his team. > > I definitely don't like the idea of maintaining two version of > telepathy-qt4. But we have to since the three packages are still > requiring the old API. Or, as Anas suggested, removed the three > packages.
The situation was such that there was an API/ABI break for Telepathy-Qt4. This was announced in meego-dev and meego-packaging: http://lists.meego.com/pipermail/meego-packaging/2011-January/246358.html as it was described in http://wiki.meego.com/Release_Engineering/Submission_Checklist Step 5: If API/ABI changes. Then we've filed bugs for applications depending on Telepathy-Qt4: https://bugs.meego.com/show_bug.cgi?id=12315 https://bugs.meego.com/show_bug.cgi?id=12332 also mailed application maintainers. We've also provided compat packages to make the transition smooth. Exact way of pushing compat packages were agreed with MeeGo architects after an indeed rather long email exchange. compat package was supposed to be there for a short time while migration but the problem was such that applications depending on Telepathy-Qt4 was not maintained at all. At that point it was agreed that then applications could be dropped, which did not seem to happen. Once that was done, compat packages could be removed. Then meego-handset-chat failing in T:T was announced and replied by Paolo: http://lists.meego.com/pipermail/meego-packaging/2011-February/246698.html http://lists.meego.com/pipermail/meego-packaging/2011-February/246704.html Please notice that my team has not been formally responsible for Telepathy on MeeGo for a while. If you'd like to learn even more about the technical aspects on what has happened Senko or Paolo (cc'd) could help though. Best Regards, -Baris _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
