Re: LDAP SDK and source repositories

On 27/07/2009 13:24, Robert Kaiser wrote:
> Mark Banner wrote:
>> This isn't urgent, but I would like to get agreement on the way forward
>> in the next few of weeks so that we know in which direction we are
>> heading.
>
> And just moving development of the c-sdk into comm-central isn't an
> option? How much is it actually used outside of comm-central?

It isn't just the c-sdk: http://mxr.mozilla.org/mozilla/source/directory/

There is the java-sdk and a perl implementation as well, plus a few 
other things.

These are released separately (from TB or SM) and I believe other 
projects do use them.

It is a valid possibility, though historically (afaik because of the 
separate releases) we've kept the SDKs separate so we can pull across 
stable versions (just like mozilla-central does with NSS etc) and not 
restrict/limit the SDKs to our development cycles, which I think would 
happen if the SDKs were included directly in comm-central.

> BTW, I had another user complaining about not being able to do libxul or
> even XULRunner builds of our apps, and he said that some LDAP code was
> where he saw breakage - if that was the c-sdk and not the xpcom stuff
> then we might want to do a significant patch pass to enable this one time.

It would be the XPCOM code, and assuming I've not missed anything, there 
is no point in doing a patch. To build with libxul you'd need to also 
fix up autocomplete (including transitioning to toolkit) and finish the 
transition of mailnews to the frozen api (there are bugs on all of 
this). If you then wanted to do xulrunner, you'd also need to remove the 
app and mailnews specific ifdefs that we have in core.

However this is part of the response is going off-topic, so if we want 
to follow this up further we should do so under a different newsgroup/topic.

Standard8