All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Reemts <lars.reemts@finalbit.de>
To: buildroot@busybox.net
Subject: [Buildroot] License for patches
Date: Wed, 24 Aug 2011 17:25:20 +0200	[thread overview]
Message-ID: <4E5517E0.30003@finalbit.de> (raw)

Hi there,

we are using Buildroot in an embedded Linux project for one of our
customers. Discussing with the customer's lawyer the steps required by
the customer in order to conform to the various open-source licenses
involved, the following issue came up:

Buildroot is licensed under the GPL. The packages buildroot builds are
licensed under different licenses. Some of these liceses are
incompatible with the GPL (e.g. the BSD style license of openssl or the
LGPL license of uClibc).

Which license is relevant for the package specific patches distributed
by buildroot? Formally it must be the GPL. But if the patches are
distributed under the GPL, this would result in an unresolvable license
collision for some packages (e.g. openssl). All other patched packages
would be infected by the GPL which would forbid dynamic linking of a
proprietary software with e.g. uClibc.

I'm sure there must be a resolution but I have been unable to convince
the lawyer so far. What can I tell him to make him happy again?

Any ideas?

Best regards

Lars Reemts

             reply	other threads:[~2011-08-24 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 15:25 Lars Reemts [this message]
2011-08-24 16:05 ` [Buildroot] License for patches Mike Frysinger
2011-08-24 16:14   ` Grant Edwards
2011-08-24 16:55     ` Yann E. MORIN
2011-08-24 20:48       ` Peter Korsgaard
2011-08-24 17:13     ` Mike Frysinger
2011-08-24 17:38       ` Grant Edwards
2011-08-24 18:08         ` Mike Frysinger
2011-08-24 20:47       ` Peter Korsgaard
2011-08-29 12:32         ` Thomas Petazzoni
2011-08-24 16:21   ` Robin Holt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E5517E0.30003@finalbit.de \
    --to=lars.reemts@finalbit.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.