After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 744718 - Provide backend specific extensions as public
Provide backend specific extensions as public
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: general
3.13.x (obsolete)
Other Linux
: Normal normal
: Future
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks: 692555
 
 
Reported: 2015-02-18 16:21 UTC by Georges Basile Stavracas Neto
Modified: 2015-03-24 06:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Georges Basile Stavracas Neto 2015-02-18 16:21:39 UTC 
Currently, Evolution and GNOME Calendar (and possibly some other clients) share the exact same code from ESourceLocal.

Exporting it as a public extension would avoid code duplication, and definitely would avoid async code.
Comment 1 Milan Crha 2015-02-18 16:31:16 UTC 
Thanks for a bug report. I agree, I also do not like code duplication and maintaining two versions of the same file in two projects (evolution has its copies of the files as well). It's not about the local calendar only, this is related to:
   addressbook/backends/ldap/e-source-ldap.c
   calendar/backends/contacts/e-source-contacts.c
   calendar/backends/file/e-source-local.c
   calendar/backends/weather/e-source-weather.c
Comment 2 Milan Crha 2015-03-24 06:27:41 UTC 
Created commit abfc938 in eds master (3.17.1+)
Created commit_0805487 in evo master (3.17.1+) [1]

[1] https://git.gnome.org/browse/evolution/commit/?id=0805487