GNOME Bugzilla – Bug 341803
ximian-connector-setup should better be renamed to exchange-connector-setup
Last modified: 2021-05-20 23:15:23 UTC
Please describe the problem: shouldn't it be better if we rename the existing ximian-connector-setup to be exchange-connector-setup, which makes more sense to the users? Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
i second this. also, no user reporting a bug will ever find out that he has to use "connector". let's change this to "evolution exchange" in bugzilla. assigning this to harish.
Created attachment 65654 [details] [review] sun_patches replace "ximian" by "exchange"
Nancy, please use cvs diff -u to make the patch again.
Created attachment 65983 [details] [review] sun_patches
Comment on attachment 65983 [details] [review] sun_patches Remove the extra whitespace on the following lines prior to commit. >+ exchange-connector-setup \ >+exchange_connector_setup_LDADD = \
* Updated Product Name/Description in Bugzilla accordingly. * The patch looks fine but I will let Sushma who maintains evolution-exchange to formally give a consent. * Pending Actions: a. s// references to ximian-connector in EDS, User Docs. b. References in Web sites, support documentation. c. Anything else that I am missing ? Kindly leave this bug unresolved till pending actions are completed.
Created attachment 66042 [details] [review] sun_patches "ximian-connector-setup" isn't referenced by other files.
The patch looks fine. Sushma ?
Can be committed to head. Also this is a duplicate bug report.
*** This bug has been marked as a duplicate of 338856 ***
I beg to differ. Bug #338856 is about the necessity of ximian-connector-setup and the desired Next Action would be to let the plugin read configuration files and get rid of the binary. This bug is about renaming it (while it still exists) and favoring the name evolution-exchange over ximian connector on all places of reference - out of the scope of the above said bug.
harish, committed the patch to CVS HEAD. Thanks.
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.