Other than libedataserverui, none of the other libraries are any different for GNOME 3 vs 2.

(In reply to comment #1)
> Other than libedataserverui, none of the other libraries are any different for
> GNOME 3 vs 2.

Not quite. /usr/lib64/evolution-data-server-1.2/extensions/libecalbackendweather.so links to gweather (2.x or 3.x) which links to gtk+ (which I *do* noted at the end).

Also the packages should be parallel installable so they cannot keep files in the same place (even if the are duplicate). Alternativly they can be separated in other package.

No, the only reason we're temporarily keeping gtk2 compatibility is for MeeGo.  This is not meant to be installed in parallel -- use one or the other.

Please read: http://mail.gnome.org/archives/desktop-devel-list/2010-June/msg00142.html

"Any library that links to gtk+, gdk or gdk-pixbuf, that switches to gtk3 will need to have the new version be separate from and parallel installable with the old version."

e-d-s 2.x and e-d-s 3.x have to be parallel installable as they are libraries and they links to gtk+ 3.0.

And we have done that for libedataserverui.  The weather calendar backend has no effect on these other libraries.

(In reply to comment #5)
> And we have done that for libedataserverui.  The weather calendar backend has
> no effect on these other libraries.

Not quite:

1. It has to be *parallel* *installable* - not just versioned. In other words if I install e-d-s 2.30.x (./configure && make all install) and e-d-s 3.x (./configure && make all install) they should not confict (do not override each other files etc.)

Here 2 packages which are suppose to be parallel installable have the same files. The gtk-3 dependent files can be separated however. i.e. there can be 3 packages - 2 separated for different versions of gtk-3 (e-d-s-ui 3.x and e-d-s-ui 2.x) parallel installable and one with common files on which the other two depends.

2. /usr/lib64/evolution-data-server-1.2/extensions/libecalbackendweather.so is *not* versioned. It is installed in 'common' folder.

I read the link at comment #4 and also discussed on irc. I just want to know if the distros will be shipping apps which will depend on gtk2 and gtk3.

If there is going to be a need for running apps based on gtk2 + gtk3 that use eds, its worth adding parallel support here.. I understand the comment #4 states parallel installable is needed, but I just want to check the cases as well before re-opening the bug.

(In reply to comment #7)
> I read the link at comment #4 and also discussed on irc. I just want to know if
> the distros will be shipping apps which will depend on gtk2 and gtk3.
> 

I think so. At least some nearly-3rd-party applications uses e-d-s and they might want to wait for some reasons with porting to 3.0 (for example to still support distros which did not move to 3.0).

> If there is going to be a need for running apps based on gtk2 + gtk3 that use
> eds, its worth adding parallel support here.. I understand the comment #4
> states parallel installable is needed, but I just want to check the cases as
> well before re-opening the bug.

On my system only tracker links to e-d-s (except core GNONE) and I'm not sure when they will be moving. Outside that there are some small apps (sorry I cannot name them as I don't remember the names - some should be on gnome-files). In the gentoo portage there are also following packages (outside core packages & tracker that depends on it) directly depending on e-d-s:

 - app-mobilephone/gnome-phone-manager
 - app-mobilephone/obexd
 - app-office/glabels
 - app-office/openoffice
 - dev-ruby/revolution
 - dev-vcs/giggle
 - gnome-extra/contacts
 - gnome-extra/tasks
 - net-im/pidgin

I'd be surprised if all of the above would be ported before 3.0 release - especially app-office/openoffice which is not released very often.

(In reply to comment #8)
>  - app-mobilephone/gnome-phone-manager
>  - app-mobilephone/obexd
>  - app-office/glabels
>  - app-office/openoffice
>  - dev-ruby/revolution
>  - dev-vcs/giggle
>  - gnome-extra/contacts
>  - gnome-extra/tasks
>  - net-im/pidgin

Which of these apps link -specifically- to libedataserverui?

If they're only linking to libecal or libebook, there is no impact.

(In reply to comment #9)
> (In reply to comment #8)
> >  - app-mobilephone/gnome-phone-manager
> >  - app-mobilephone/obexd
> >  - app-office/glabels
> >  - app-office/openoffice
> >  - dev-ruby/revolution
> >  - dev-vcs/giggle
> >  - gnome-extra/contacts
> >  - gnome-extra/tasks
> >  - net-im/pidgin
> 
> Which of these apps link -specifically- to libedataserverui?
> 
> If they're only linking to libecal or libebook, there is no impact.

1. Doesn't libecal load /usr/lib64/evolution-data-server-1.2/extensions/libecalbackendweather.so?
2. http://www.mail-archive.com/devel@lists.fedoraproject.org/msg07183.html:
It seems Fedora have some packages depending on libedataserverui-1.2:
- almanah (links to libedataserverui)
- anjal

(In reply to comment #10)
> 1. Doesn't libecal load
> /usr/lib64/evolution-data-server-1.2/extensions/libecalbackendweather.so?

No.  Only the calendar D-Bus service uses that extension.

> 2. http://www.mail-archive.com/devel@lists.fedoraproject.org/msg07183.html:
> It seems Fedora have some packages depending on libedataserverui-1.2:
> - almanah (links to libedataserverui)
> - anjal

Anjal is a dead package and there's already a strong push to move MeeGo 1.1 (for which almanah is a bas library) to GTK3.

almanah - http://git.gnome.org/browse/almanah/tree/configure.ac#n87

> almanah - http://git.gnome.org/browse/almanah/tree/configure.ac#n87

Ups. Sorry I haven't notice in previous discussion.