Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Allow PHP to compile ans link with berkeleydb 6
Date: Tue, 08 Oct 2013 09:20:20 +0200	[thread overview]
Message-ID: <5253B234.60001@mind.be> (raw)
In-Reply-To: <20131007145734.781254cd@skate>

On 10/07/13 14:57, Thomas Petazzoni wrote:
> Dear Gustavo Zacarias,
>
> On Mon, 07 Oct 2013 09:30:16 -0300, Gustavo Zacarias wrote:
>> On 10/07/2013 09:26 AM, Thomas Petazzoni wrote:
>>
>>> Sorry, I forgot to add a smiley or something. To be "how useful
>>> BerkleyDB can be with PHP" was ironic, so I was actually meaning that I
>>> don't think PHP+BerkeleyDB is so useful, so that to me, the first
>>> option is perfectly acceptable.
>>
>> Seems to be useful to Jerome maybe since he cared about fixing it.
>> That being said the license is rotten and not only for PHP, we should
>> just stick away from bdb6 IMHO.
>
> Ok, so as discussed on IRC, my proposal would be:
 >
 >   * Downgrade the berkeleydb package to the last known non-AGPL version
 >     (i.e essentially revert commit
 >     4c478de2e76ffc1d0a6dc413475307fd44a0a595). This way, all existing
 >     packages in Buildroot that rely on berkeleydb continue to work with
 >     no change, and don't create a legal issue. Add a comment in the
 >     berkeleydb.mk file that explains why it shouldn't be bumped to v6 of
 >     the project.
 >
 >   * If someone cares, integrate an additional berkeleydb6 package that
 >     packages the v6 of berkeleydb under AGPL.

  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.

  I took a quick look at which other packages are using berkeleydb. Most 
of them are compatible with GPL.

netatalk: GPLv2+ -> compatible (note that _LICENSE is missing)
perl: Aristic is not compatible, but GPLv1+ is (note that _LICENSE is wrong)
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...


  Regards,
  Arnout

> J?r?me, are you interested in doing such work?
>
> Best regards,
>
> Thomas
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-10-08  7:20 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 [this message]
2013-10-08  8:01             ` Thomas Petazzoni
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=5253B234.60001@mind.be \
    --to=arnout@mind.be \
    --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