Re: [Opensync-devel] binary package build scripts

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

On Sun, Sep 05, 2010 at 01:27:40PM +0300, Juha Tuomala wrote:
> I'm for example maintaining pkgs for Fedora and even run Koji build
> system of my own. Lack of packages is not a problem.

Cool!  Are your spec files, etc, available in SVN somewhere in case
I wish to follow them personally?  If packages are already available,
I don't want to duplicate effort, but when opensync is completely
gone from Debian Squeeze (both 0.22 and 0.3x), it has me worried,
and someone should stay on top of it.


> Our problem was that there were packages in Fedora which were from 
> 0.2x branch and everyone was reporting bugs/focusing on those. I
> even tried hard to get them to drop those without luck.
> 
> Then we had problem that development broke too many things that
> SCM HEAD was unusable and didn't really make sense to ship even
> for testing.

I remember when Fedora went to 0.3x.  And the API breakage was expected.
I don't think any 0.3x version should be in an official distro, unless
0.22 is there beside it.

But I *do* think that binary packages for 0.3x should be available
somewhere, for those that wish to test.  There are some 0.3x in
Debian experimental... I assume you have some for Fedora?
Not sure about openSuSE.


> The question is, has that change recently? I tried to ask
> this from core developer, but never got any reply.
> 
> There is plenty of people waiting to join back to the minor tasks
> for opensync if there actually would be something to do.

That's great to hear.  Are there any programmers in that set, or are
we talking about packaging tasks?

Are their packages for the 0.3x plugins yet?

As soon as a significant number of plugins are ported over, I think
we should release 0.4x.  So far, the status is:

	Evolution: done
	Barry: done
	File-sync: done
	Ldap: I think done, but I need to give it a test run
	Google-calendar: 50% done, only calendar

Anyone with a syncml phone willing to test the syncml stuff and report
whether it's done or not?

Thanks,
- Chris