I'm attaching a couple of useful OpenLDAP schemas which significantly enhance the usability of evolutions's contact database when using an LDAP server as a contact data repository. I dug these up on the Internet, where the last discussion and development on them dates from 2002. Perhaps they should be resurected and included with either the OpenLDAP ebuild or the evolution ebuild (USE=ldap set). The first one, evolutionperson.schema implements many attributes which evolution attempts to store when a contact record is saved to an LDAP database. The 2nd one, calentry.schema adds an entry for a Calendar URI (calCalURI) and a Free/Busy URL (calFBURL) as per RFC2739. It should be noted that if these schemas are _not_ included, and any of the implemented fields in an evolution contact record contain data, say from a personal (local) contact list, and an attempt to save the record to an LDAP database, the save will fail silently, logging an "attribute type undefined" error (if logging is enabled).
Created attachment 52562 [details] evolutionperson.schema - Schema for various fields implemented in evolution contacts
Created attachment 52563 [details] calentry.schema - RFC2739 calendar entries used by evolution
gnome: install schemas to /etc/openldap/schema
> gnome: I think the install dir is DM-neutral
It looks like evolutionperson.schema is already included with the evolution-data-server ebuild, can we get the RFC2739 schema included as well?
Is this fixed?
no news about this for some time. I guess the simplest way to go is to add some einfo to the eds ebuild to tell the user where to get those schemas if he needs them.
Evolution was just moved to gnome herd, reassigning appropriately
ok here is what I'm proposing to do and that I shall implement this week unless someones cries out loud. * add these schemas to the tree if they are not present in any package (I'm thinking of calentry here), this way they have a permanent, versioned location which isn't true anywhere else on the web that I can remember. * we then install them in proper /etc/openldap/schemas folder with USE=ldap * and add en elog about it so that users needing this will find it easily. * profit and close this damn bug. thoughts ?
Sounds fine to me.
done in 2.24.*
