8
full text of the GPL (either through the above link, or in the le LICENSE in the BusyBox
tarball), and also read the Frequently Asked Questions about the GPL.
If you distribute GPL-licensed software the license requires that you also distribute the
source code to that GPL-licensed software. If you distribute BusyBox without making the
source code to the version you distribute available, you violate the license terms, and
thus infringe on the copyrights of BusyBox. This requirement applies whether or not you
modied BusyBox; either way the license terms still apply to you.
License enforcement
BusyBox’s copyrights are enforced by the Software Freedom Law Center (you can contact
them at gpl@busybox.net), which “accepts primary responsibility for enforcement of US
copyrights on the software... and coordinates international copyright enforcement efforts
for such works as necessary.” If you distribute BusyBox in a way that doesn’t comply with
the terms of the license BusyBox is distributed under, expect to hear from these guys.
Their entire reason for existing is to do pro-bono legal work for free/open source software
projects. We used to list people who violate the BusyBox license in The Hall of Shame, but
these days we nd it much more effective to hand them over to the lawyers.
Our enforcement efforts are aimed at bringing people into compliance with the BusyBox
license. Open source software is under a different license from proprietary software, but
if you violate that license you’re still a software pirate and the law gives the vendor (us)
some big sticks to play with. We don’t want monetary awards, injunctions, or to generate
bad PR for a company, unless that’s the only way to get somebody that repeatedly ignores
us to comply with the license on our code.
My company wants to include BusyBox into a product. What do we need
to do in order to comply with BusyBox’s license?
First: DON’T PANIC. Complying with BusyBox’s license is easy. Complying with
BusyBox’s license doesn’t cost any money. If, after reading the license and this document
something is not clear to you, please send emails with your questions to the BusyBox
mailing lists. We will expand this document to cover them.
If you are distributing the BusyBox binary, you also have to distribute the corresponding
source code. If you modied the source, you have to distribute the modied source.
The text of the license obliges you to provide source code for binaries you distribute, and
gives you exactly three options for providing source code. These options are spelled out
in section 3 of the LICENSE le in the BusyBox source tarball:
3A) bundle the complete corresponding source with the binary.
3B) bundle a written offer good for three years to provide source upon request (these
days this is often a URL).
3C) point you users at the upstream source (i.e. pass along somebody else’s 3B offer).
Using option 3A, that is, putting exact BusyBox source and .cong le you used to build
the binary on the same medium which you use to ship the binary, is the most bullet-
proof approach to license compliance. If you do that, you can stop reading, your license
obligations have been satised.
Comentarios a estos manuales