From: Mark Hatle <mark.hatle@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/6] db: Uprev to 6.0.30
Date: Tue, 1 Jul 2014 16:12:25 -0500 [thread overview]
Message-ID: <53B32439.6050804@windriver.com> (raw)
In-Reply-To: <CAJTo0LYnb4YifRMXyPdaX7ZQMBvT3Hw2S9bN-q4Uxmiz2x3efw@mail.gmail.com>
On 7/1/14, 3:56 PM, Burton, Ross wrote:
> On 1 July 2014 21:01, Mark Hatle <mark.hatle@windriver.com> wrote:
>> +LICENSE = "AGPL-3.0"
>
> Presumably AGPL-v3 has the same clauses that caused
> INCOMPATIBLE_LICENSES to exist?
>
> Does this mean that we should update the documentation to add AGPL-3.0
> to the list of licenses being blacklisted in no-v3 builds, and that in
> no-v3 images we can't have rpm on the target?
I'm not sure. We likely need someone (with a legal background) to investigate
and let us know.
Baring that, it's likely that AGPL-3.0 has similar restrictions to GPL v3 and
LGPL v3.
This might make it worthwhile in keeping the older Sleepycat licensed version
around and making related changes to RPM to allow use of the older version if
appropriate.
--Mark
> Ross
>
next prev parent reply other threads:[~2014-07-01 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 20:01 [PATCH 0/6] RPM, BerkleyDB and related changes Mark Hatle
2014-07-01 20:01 ` [PATCH 1/6] lib/oe/package_manager.py: Fix _pkg_translate_smart_to_oe function Mark Hatle
2014-07-01 20:01 ` [PATCH 2/6] db: Uprev to 6.0.30 Mark Hatle
2014-07-01 20:56 ` Burton, Ross
2014-07-01 21:12 ` Mark Hatle [this message]
2014-07-03 7:46 ` Anders Darander
2014-07-03 13:42 ` Burton, Ross
2014-07-10 11:39 ` Anders Darander
2014-07-10 11:56 ` Anders Darander
2014-07-01 20:01 ` [PATCH 3/6] rpm: Upgrade to 5.4.14 Mark Hatle
2014-07-01 20:01 ` [PATCH 4/6] rpm: Replace patch with backport from SCM version of RPM5 Mark Hatle
2014-07-01 20:01 ` [PATCH 5/6] package_rpm.bbclass: Should be using HOST_* not TARGET_* Mark Hatle
2014-07-01 20:01 ` [PATCH 6/6] rpm_5.4+cvs: Add RPM community tree for future development Mark Hatle
2014-07-02 15:55 ` [PATCH 0/6] RPM, BerkleyDB and related changes Mark Hatle
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=53B32439.6050804@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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