[meego-packaging] [meego-commits] 15527: Changes to Trunk:Testing/compat-telepathy-qt4
nashif at linux.intel.com
Fri Apr 1 04:01:13 PDT 2011
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.
- 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.
On 1 Apr 2011, at 11:46, <mikhail.zabaluev at nokia.com> <mikhail.zabaluev at nokia.com> wrote:
>> -----Original Message-----
>> From: ext Zhu, Peter J [mailto:peter.j.zhu at intel.com]
>> Sent: Friday, April 01, 2011 6:56 AM
>> To: meego-packaging at meego.com; Zabaluev Mikhail (Nokia-MS/Helsinki)
>> Cc: Hofemeier, Ulf
>> Subject: RE: [meego-commits] 15527: Changes to Trunk:Testing/compat-
>>> - Drop the development packages from the compatibility package
>> 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.
> Sorry for not spelling out all this in the submission or the changelog. I must be spoiled by submitting packages to mainstream distributions, where the gatekeepers normally possess a sufficient level of clue to investigate why the change is made if the accompanying notes are too terse, rather than bouncing it right off the bat, and remember the meaning of naming conventions like compat-. Maybe that's too much to expect in MeeGo.
> MeeGo-packaging mailing list
> MeeGo-packaging at meego.com
More information about the MeeGo-packaging