Re: [Opensync-devel] opensync and Debian

[Chris F. <cd...@fo...>]

On Fri, Mar 12, 2010 at 01:34:44AM +0100, Michael Banck wrote:
> Well, making it possible to run both and actually supporting the stable
> version are two different things.  If you look at the trac list for
> 0.22, you see loads of tickets which look fatal.  AFAICT, there were two
> commits on the 0.2x branch in the last 2-3 years.
> 
> Maybe it is my fault, but I stopped fowarding (or even looking) at 0.22
> bugs in Debian for a while now, assuming nobody else cares, either.

While people aren't caring enough to fix bugs in 0.22, and while the
0.22 platform is shakey, it is still useable.  Is it not ok to consider
0.22 as legacy software, only available for people to use if it works
for them, but no support?


> I believe the story is: libsyncml-0.4.7 (I think) and above use
> libsoup-2.4, while the others use libsoup-2.2.  The syncml plugin for
> opensync-0.22 only works with libsyncml-0.4.6 (I think) and lower.

Are these simple API changes, or wholesale APIs removed or changed?
Going from 0.4.6 to 0.4.7 doesn't look like a huge change, from the
version numbers.  Is this patchable?  Is it worth my time to send a
patch to you?


> I really don't want to point fingers, and I take the blame for the wrong
> upload, but in the end, I would have just as well removed opensync-0.22
> for the next stable release even if 0.3x would still be in experimental.

I have a hard time with this.  This just makes it even harder for
users who want to sync with opensync.  Maybe people use 0.22 and then
give up later due to bugs, but I know that some folks are quite happy
that *any* form of sync is available for them on Linux.  Whether there
are bugs or not.

If the next stable has no opensync at all, where will these users go?

- Chris