Hi > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Friday, April 01, 2011 7:14 PM > To: [email protected] > Cc: Zhu, Peter J; [email protected]; Hofemeier, Ulf; > [email protected] > Subject: RE: [meego-packaging] [meego-commits] 15527: Changes to > Trunk:Testing/compat-telepathy-qt4 > > Hi, > > > -----Original Message----- > > From: ext Anas Nashif [mailto:[email protected]] > > Sent: Friday, April 01, 2011 2:01 PM > > To: Zabaluev Mikhail (Nokia-MS/Helsinki) > > Cc: [email protected]; [email protected]; > > [email protected] > > Subject: Re: [meego-packaging] [meego-commits] 15527: Changes to > > Trunk:Testing/compat-telepathy-qt4 > > > > 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. Peter > Best regards, > Mikhail > > > On 1 Apr 2011, at 11:46, <[email protected]> > > <[email protected]> wrote: > > > > > Hi, > > > > > >> -----Original Message----- > > >> From: ext Zhu, Peter J [mailto:[email protected]] > > >> Sent: Friday, April 01, 2011 6:56 AM > > >> To: [email protected]; Zabaluev Mikhail (Nokia-MS/Helsinki) > > >> Cc: Hofemeier, Ulf > > >> Subject: RE: [meego-commits] 15527: Changes to Trunk:Testing/compat- > > >> telepathy-qt4 > > >> > > >>> - Drop the development packages from the compatibility package > > >> set > > >>> (BMC#13291) > > > > > >> This is totally wrong submission. Devel packages are totally > > removed, > > >> which result in libmeegochat/meego-handset-chat/meegotouchcp-chat > > fail. > > >> Would revert. > > > > > > Have you tried to look into the bug that this change fixes? > > > The problem is precisely that there are now two conflicting > > development packages for Telepathy-Qt4. > > > The purpose of package compat-telepathy-qt4 is to provide the > > binaries for the 0.4 branch for backwards compatibility. The > > development files for Telepathy-Qt4 (version 0.5.x) are now provided by > > the package telepathy-qt4-devel, built out of telepathy-qt4 (updates to > > which you are blocking for other reasons). > > > Leaving the -devel packages in this compatibility stub was a mistake, > > and it created problems in the distribution. _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
