So even if i'm only dynamically linking to libcurl, I need to include the
license?

--pete

> -----Original Message-----
> From: SM [mailto:nntp_at_iname.com]
> Sent: Wednesday, July 11, 2001 9:58 AM
> To: curl-library_at_lists.sourceforge.net
> Subject: Re: License issues with base64.c in libcurl
>
>
> At 12:28 11-07-2001 +0800, Andrew Francis wrote:
> >I'm again confused, but in a different way. Could someone
> quickly outline
> >what I must do to comply with the curl license, to use it in a
> >closed-source project?
>
> You have to include the copyright notice(s) and the
> permission notice in
> the supporting documentation for your closed-source project.
>
> >I've put a copy of my base64.c replacement at the following
> URL. I'd be
> >happy to cede copyright or whatever yucky legal stuff is
> required to make
> >this slot nicely into curl.
> >
> > http://members.iinet.net.au/~locust/base64.c
>
> Thanks for the code. I suggest that you raise this issue
> with Daniel when
> he returns from his vacation.
>
> Regards,
> -sm
>
> _______________________________________________
> Curl-library mailing list
> http://curl.haxx.se/libcurl/
>

_______________________________________________
Curl-library mailing list
http://curl.haxx.se/libcurl/
Received on 2001-07-11