[Evolution] Ldap, Evo and evolutionPerson.schema

2002-09-25 Thread Tony Earnshaw
Hi developers, Chris Toshok wrote 16th August last: The location of the schema file wasn't communicated that well even to the people that *did* use the source instead of binary snapshots. The reason being it was a hack and even when I wrote it I knew most of it would end up being deprecated

Re: [Evolution] Ldap, Evo and evolutionPerson.schema

2002-09-25 Thread Adam Williams
> >The location of the schema file wasn't communicated that well even to >the people that *did* use the source instead of binary snapshots. The >reason being it was a hack and even when I wrote it I knew most of it >would end up being deprecated eventually (parts of it already are -- the >calenda

Re: [Evolution] Ldap, Evo and evolutionPerson.schema

2002-09-25 Thread Tony Earnshaw
ons, 2002-09-25 kl. 13:21 skrev Adam Williams: > evolutionPerson is a structural class. That is probably the root of the > problem. Nope. 2.1.4 would not have worked then. The complaint is about the attribute, not the objectClass, nor any objectClass conflict. I've had them with the Evo schema