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: Mon, 7 Oct 2013 14:26:14 +0200 [thread overview]
Message-ID: <20131007142614.45304395@skate> (raw)
In-Reply-To: <5252A7DF.5020008@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 07 Oct 2013 09:23:59 -0300, Gustavo Zacarias wrote:
> On 10/07/2013 08:57 AM, Thomas Petazzoni wrote:
> > Therefore, linking PHP with BerkeleyDB version 6 creates a PHP binary
> > that cannot legally be distributed.
> >
> > If this analysis is correct, I'd suggest one of the following options:
> >
> > * Drop the support for BerkeleyDB support in PHP.
> >
> > * Add a berkeleydb5 package that packages the last known non-AGPL
> > version of BerkeleyDB, and use that for PHP.
> >
> > Considering how useful BerkeleyDB can be with PHP, I'm suggesting the
> > first option.
>
> You mean the second option right?
> Otherwise you're conflicting with yourself ;)
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.
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-07 12:26 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 [this message]
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
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=20131007142614.45304395@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 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.