[SyncEvolution] SyncEvolution 1.1.99.2 ready for testing

[Peter Robinson]

On Thu, Feb 10, 2011 at 7:49 AM, Patrick Ohly <patrick.ohly at gmx.de> wrote:
> On Mi, 2011-02-09 at 22:28 +0000, Peter Robinson wrote:
>> Two issues. First one is easy, is there a source file? :-)
>
> Yes, but I have been hiding it so that people don't start packaging
> it ;-)
>
> http://downloads.syncevolution.org/syncevolution/sources/experimental/syncevolution-1.1.99.2.tar.gz
>
> Seriously, I'd rather have some folks here on this list test that
> version before it gets rolled out to some unsuspecting distro users. The
> next version should be suitable for an unstable distro again.

I'm not planning on pushing it to an "unsuspecting distro user" I push
it through my build system and test that it will compile on Fedora
rawhide using gcc 4.6 and all the fun things its introducing to give
"upstream" details of any issues so that they may review them within a
reasonable time.

>> Second one is a query about the libgdbus fork. Its causing me a lot of
>> problems in Fedora. There are now a number of packages using the
>> upstream version including gupnp (which is now used by parts of gnome
>> 3) which is causing problems in Fedora and basically makes
>> syncevolution unusable in a lot of cases. What are the plans on
>> getting your patches upstream?
>
> If you talk about the gdbus in glib [1], that is not the upstream of the
> code in SyncEvolution. The upstream is the older gdbus from Marcel
> Holtmann [2] from the Bluez tools.

Yes, the one from Marcel is the one I'm talking about (we've had this
conversation before and I do remember it).

> Why is the usage of the Bluez gdbus a problem? I thought we had resolved
> the name clash by renaming the symbols in the SyncEvolution source code.

Why is the submission of patches upstream a problem?

As for chaanges of namespaces as far as I can tell its been shoved it
into a sub directory of syncevolution. The readme in the source tells
me as much when it documents the script to split out the patches. With
it in a sub directory the standard build of syncevolution doesn't find
it because its not in the ld path, if you add it to the path it
conflicts with the other library if installed.

> If someone has a patch which allows to switch between the Bluez gdbus
> and glib gdbus, then I'd be happy to include it. I just don't have time
> to do that myself.

Personally I'd prefer if the patches were upstream and there was just
one of them and we didn't have to worry about hacks to "switch".

>> Oh and does it have the option to use both gtk2 and gtk3 as evolution
>> and e-d-s for gnome3 will require it if you use any of the e-d-s/evo
>> gui components.
>
> No, there's no support for gtk3. The sync-ui is the only component using
> GTK. It's a stand-alone process, so hopefully it'll continue to work
> even if the rest of the system moves to gtk3. The EDS backends will need
> some work to cope with API changes in Evolution 3.0 - not done yet,
> patches welcome :-/
>
> [1] http://library.gnome.org/devel//gio/2.26/gdbus.html
> [2] http://git.kernel.org/?p=bluetooth/libgdbus.git;a=summary
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.