License concerns when embedding script in busybox binary

[Sam Liddicott]

On Fri, 9 Nov 2018 16:51 Michael Conrad <mconrad at intellitree.com wrote:

> On 11/7/2018 10:49 AM, Ron Yorston wrote:
>
> Kang-Che Sung wrote:
>
> Specifically, I think the current state of config ASH_EMBEDDED_SCRIPTS
> help text did not yet warn builders that the binary may be distributed **only
> when the embedding scripts are GPLv2-compatible**. Builder and
> distributors may accidentally violate copyright if they didn't get careful
> at reading the BusyBox licenses. I think something should be done to make
> the warning more explicit.
>
> As I said: I don't know what the status of embedded scripts is. *Are*
> they required to be GPLv2 compatible?
>
> I'm not a lawyer either, but I'd guess they probably need to be. But, the
> main requirement is that a vendor provide the source to their customer, and
> the source is in fact being shipped because it's a script.  Anyone with gdb
> would be able to extract the table and then decompress it back to the
> original directory of scripts.  Maybe if busybox had an option to dump out
> the scripts it would help enforce the idea that the sources were being
> shipped.  Wonder how many bytes that would require…
>

A requirement not just to ship/provide the source, but to license it too!

Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20181110/11934c2c/attachment.html>