Hah, I guess we all know what happens when one assumes :)
Mono has some GPL bits I believe, so double check the exact licence,
but it should otherwise be OK. Also, what Jimmy said - if it's
isolated in it's own assembly there shouldn't be any issues.
- Jeff
On Tue, Aug 2, 2011 at 8:53 AM, Slide
The projects have multiple licenses because of external dependencies.
In general, if we can keep the compiler and library implementations
Apache 2 that'd be great. If we do need to bring in something with a
different license, it should be it's own assembly.
~Jimmy
On Tue, Aug 2, 2011 at 11:53 AM
No, I was actually thinking of pulling something in from Mono which has
nothing to do with zlib or zipimport :-) I am planning on reusing the
existing decompression that is currently used in the zlib module for
zipimport (which is coming along nicely by the way).
Thanks,
slide
On Tue, Aug 2, 201
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
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/
___
Ironpy
