Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4448#issuecomment-73377917
@fommil I think you're misrepresenting the nature of the LGPL issue. It is
materially different from the Apache License 2, and so bundling LGPL with
Apache Licensed code means downstream consumers of Spark suddenly are bound by
more than the restrictions of the AL2, and that would be surprising. It's a
recipe for helping people accidentally violate the license of the LGPL code
that would then be included, as it sure looks like the whole thing is AL2 (or
work-alike licenses).
It's out of respect for others' choice of licensing terms, which put
restrictions on redistribution that an Apache project does not meet, that LGPL
code can't be redistributed. Spark does not redistribute libgfortran. That's
fine, the LGPL allows linking. Clearly there's no aversion to using LGPL
software per se here.
(Or do you think that the LGPL permits redistribution in a derivative work
on the same terms as the AL2 -- is that what you mean the "FUD" is?)
People should be aware of licenses and either comply with software's terms
or not use it. As a vendor, we most certainly care quite a lot about getting it
right. I can't agree that we should all bundle whatever free software we want,
because you think it's only commercial software we have to worry about. I hope
that people out there wouldn't disregard the terms under which I license my
free software.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
