> > A few reasons: > > 1. libsmbclient is GPL > > Is there a conflict with curl's license if you provide the option? > Maintainer has to handle the rest.
No, but there would be for commercial projects using libcurl with libsmbclient. > > 3. build natively on windows > > I sure there is a built-in API in Windows. Isn't there one? > What about a simple UNC path and handle the rest over to Windows? My understanding is that Windows does not allow simultaneous connections to a share, so this was not an option for us. > For those who are interested, why don't make it like with SSL, have different > implementations, backends? LDAP has two implementations (openldap.c and ldap.c). So, someone could probably implement a separate libsmbclient implementation in the future. -Bill ________________________________ This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
