From: "Puustinen, Ismo" <ismo.puustinen@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"alexander.kanavin@linux.intel.com"
<alexander.kanavin@linux.intel.com>
Subject: Re: [PATCH v2] python3: make readline, gdbm, and db support conditional.
Date: Thu, 8 Jun 2017 12:35:15 +0000 [thread overview]
Message-ID: <1496925313.23488.6.camel@intel.com> (raw)
In-Reply-To: <75435a83-d29b-4b68-3e27-90746b31c970@linux.intel.com>
On Thu, 2017-06-08 at 13:51 +0300, Alexander Kanavin wrote:
> On 06/07/2017 04:49 PM, Ismo Puustinen wrote:
> > The three libraries' (readline, gdbm, and db) licenses belong to
> > the
> > GPLv3 family. Add them to to PACKAGECONFIG so they can be switched
> > off
> > if the licensing doesn't allow using them. Python build system
> > autodetects the dependencies but doesn't allow them to be
> > explicitly
> > disabled, so just deal with the dependencies.
>
> db should be taken out from this patch, it's no longer a gplv3
> concern
> now that we're providing db 5.x only :)
I can leave db out of the patch then. Is db 5.x a long-term solution or
do we have to change to 6.x at some point? Is anyone maintaining db 5
(security fixes especially) anymore?
Ismo
next prev parent reply other threads:[~2017-06-08 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 13:49 [PATCH v2] python3: make readline, gdbm, and db support conditional Ismo Puustinen
2017-06-07 14:10 ` Burton, Ross
2017-06-08 10:20 ` Puustinen, Ismo
2017-06-09 7:43 ` Puustinen, Ismo
2017-06-08 10:51 ` Alexander Kanavin
2017-06-08 12:35 ` Puustinen, Ismo [this message]
2017-06-08 12:37 ` Alexander Kanavin
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=1496925313.23488.6.camel@intel.com \
--to=ismo.puustinen@intel.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.