Unfortunately, I'm not entirely sure. We do include the Python & Ruby
stdlibs, which have their own licenses, and zlib.net, which is
MIT/BSD. I'm going to hazard a guess that you're thinking of #ZipLib,
which is GPL + Classpath, which isn't as scary as it sounds, but still
makes me slightly nervous. I'd prefer to avoid it if possible. At the
very least, it might be an external, optional dependency.

On that note, I did happen across
https://github.com/IronLanguages/main/blob/master/Hosts/Silverlight/Chiron/Zip.cs
that you might find interesting.

- Jeff

On Mon, Aug 1, 2011 at 9:30 PM, Slide <slide.o....@gmail.com> wrote:
> What are the guidelines for bringing in part or all of an external library?
> What licenses are compatible with the rest of the IP source code so it won't
> be tainted by anything?
> Thanks,
> slide
>
> --
> slide-o-blog
> http://slide-o-blog.blogspot.com/
>
> _______________________________________________
> Ironpython-users mailing list
> Ironpython-users@python.org
> http://mail.python.org/mailman/listinfo/ironpython-users
>
>
_______________________________________________
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpython-users

Reply via email to