Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Allow PHP to compile ans link with berkeleydb 6
Date: Tue, 8 Oct 2013 10:01:41 +0200	[thread overview]
Message-ID: <20131008100141.252ec3ae@skate> (raw)
In-Reply-To: <5253B234.60001@mind.be>

Dear Arnout Vandecappelle,

On Tue, 08 Oct 2013 09:20:20 +0200, Arnout Vandecappelle wrote:

>   I didn't follow the conversation on IRC, but IMHO this proposal has 
> important political implications.  With this change, we are taking a 
> stand: non-copyleft software should be the default. So in my opinion,
> we should instead make the default berkeleydb v6 and add a
> berkeleydb5 package for PHP.

This solution is also fine with me. In the mean time, I still believe
reverting the patch that bumps to v6 is for the moment the best action
to take, until someone steps up to make the change to berkeleydb v6.

However, AGPLv3+ (the new license of berkeleydb) is a fairly strong
license, so I'm quite sure a number of embedded system markers would be
interested in having the ability to build Python, or Perl, against a
non-strongly-copyleft licensed version of berkeleydb.

> netatalk: GPLv2+ -> compatible (note that _LICENSE is missing)
> perl: Aristic is not compatible, but GPLv1+ is (note that _LICENSE is
> wrong)

But aren't all Perl modules licensed under the Artistic license? Not
sure if it can cause some problems with berkeleydb being AGPLv3+,
though.

> python: PSF license v2 is compatible
> ruby: Ruby license is probably incompatible, but BSD-2c is (note that 
> _LICENSE is wrong). Unfortunately, there are also a few incompatible 
> files in the ruby distribution.
> 
>   Footnote: except for python, none of the licenses above are
> actually correctly defined in buildroot. This worries me...

Well, licensing information is tricky to get right. I believe the kind
of review you made is typically what makes the licensing information
progressively better.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-08  8:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 11:42 [Buildroot] [PATCH] Allow PHP to compile ans link with berkeleydb 6 Jérôme Pouiller
2013-10-07 11:57 ` Thomas Petazzoni
2013-10-07 12:23   ` Gustavo Zacarias
2013-10-07 12:26     ` Thomas Petazzoni
2013-10-07 12:30       ` Gustavo Zacarias
2013-10-07 12:57         ` Thomas Petazzoni
2013-10-07 19:21           ` Jérôme Pouiller
2013-10-08  7:20           ` Arnout Vandecappelle
2013-10-08  8:01             ` Thomas Petazzoni [this message]
2013-10-08 17:16               ` Arnout Vandecappelle
2013-10-08 18:09                 ` Thomas Petazzoni
2013-10-08 19:38                   ` Arnout Vandecappelle

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=20131008100141.252ec3ae@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox