OT: Mobile Internet Toolkit EULA
tim at vegeta.ath.cx
Tue Nov 13 05:22:32 CET 2001
-----BEGIN PGP SIGNED MESSAGE-----
Guido Stepken <stepken at little-idiot.de> graced us by uttering:
[ snipped excerpt from MS MIT EULA ]
> Thanx lots for checking this out ! Hmmm, that means, that it is forbidden
> to produce (distribute) code, consisting of (L)GPL Software and Microsoft
> OpenSource. One is not allowed to mix code. BSD License + Microsoft Code,
> that's OK !
> Any ideas, why ?
The BSD license is unrestrictive. I can take an entire BSD-licensed
file, cut-and-paste it into my own project, sign, seal, and
deliver...and not even have to mention where I got it.
This is fine by Microsoft because it means if they find anything they
want somewhere inside a Berkeley Quality Software project, they can just
What I think was even more appalling was the restriction on
: (ii) not using Potentially Viral Software (e.g. tools) to
: develop Recipient software which includes the Software,
: in whole or in part.
This means I can't
- test a script using a perl binary that falls under the (default)
- test a script using a Python binary that falls under the GPL
- _use_ Vim or Emacs to edit _any_ file in the project I'm developing.
- make a tarball of a directory tree using GNU tar or GNU gzip.
- ...and so on
Limitations on the product distributed is nothing new. OTOH, Microsoft
has just attempted to make it _ILLEGAL_ to use a python binary I've
compiled myself (though ActivePython is probably alright). _This_ is
what a _huge_ number of people are upset about.
There's something to be said for returning the whole syntax tree.
-- Larry Wall in <199710221833.LAA24741 at wall.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
More information about the Python-list