3 ms·
This is the page I have been referring to since you wrote "As far as I know, the requirement is to dump a tarball of any changes you made on a web server". Agai
by zamadatix 4y ago
This is the page I have been referring to since you wrote "As far as I know, the requirement is to dump a tarball of any changes you made on a web server". Again what's on that page and what you were saying clearly disagreed, just go back and read your original comments now that you understand the distribution requirements. Nobody has been saying the requirements are complicated just easily missed.
Despite the message of "if you do that, you can stop reading" imagine you might not always be able to do that and read on through to the following regarding option 3(b) which deals with their recommendation for what to do when you ship the binaries with firmware, the most common method of distributing copies of busybox. 3(a) is the simplest way for general software but it doesn't really make sense for the firmware distribution use case, as they note. Either way both 3(a) and 3(b) are completely different from what you were originally proposing to do and they both requiring delivering full source + build/install scripts even if you don't otherwise redistribute the source (just redistributing the binary is enough). Nothing complicated as long as you can get people to read the license page first.
So far everything here but your earlier comments agree many other licenses are easier to comply with and it's not worth worrying about. This is why the original comment recommended looking at Toybox, a BSD licensed alternative, for the reasons you just listed.
There's not any need to constantly call names or say responses are BS, the content of each message already speaks to its own value.