[oe] [meta-oe][PATCH] parted_1.8.6.bb: add parted that not GPLv3

[Andreas Müller]

On Mon, Aug 31, 2015 at 9:11 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
> On Mon, Aug 31, 2015 at 10:58 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
>> On Mon, Jul 06, 2015 at 09:51:34AM +0800, Lei Maohui wrote:
>>> In oe-core,the parted is GPLv3,so add parted-1.8.6 which is not GPLv3.
>>>
>>> Signed-off-by: Lei Maohui <leimaohui at cn.fujitsu.com>
>>> ---
>>>  .../parted-1.8.6/1000parted-1.8.6-warnings1.patch  | 11 ++++
>>>  .../1001parted-1.8.6-notransname1.patch            | 39 ++++++++++++++
>>>  .../1002parted-1.8.6-off-by-one1.patch             | 25 +++++++++
>>>  .../1003parted-1.8.6-primary-boundary1.patch       | 12 +++++
>>>  .../parted-1.8.6/1004parted-1.8.6-xvd1.patch       | 50 +++++++++++++++++
>>>  .../1005parted-1.8.6-devmapper-header1.patch       | 13 +++++
>>>  .../parted/parted-1.8.6/7000no_effect_macro1.patch | 11 ++++
>>>  .../parted/parted-1.8.6/ui.c-fix-build-error.patch | 26 +++++++++
>>>  meta-oe/recipes-extended/parted/parted_1.8.6.bb    | 62 ++++++++++++++++++++++
>>>  9 files changed, 249 insertions(+)
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/1000parted-1.8.6-warnings1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/1001parted-1.8.6-notransname1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/1002parted-1.8.6-off-by-one1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/1003parted-1.8.6-primary-boundary1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/1004parted-1.8.6-xvd1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/1005parted-1.8.6-devmapper-header1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/7000no_effect_macro1.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted-1.8.6/ui.c-fix-build-error.patch
>>>  create mode 100644 meta-oe/recipes-extended/parted/parted_1.8.6.bb
>>
>> I cannot take this to meta-oe, because as soon as it's added there it
>> will be used by all DISTROs even those who don't mind having GPLv3
>> version.
>>
>> Everybody would need to define PREFERRED_VERSION, because
>> DEFAULT_PREFERENCE is useless across different layers :/
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=2964
>>
>> So this either has to be introduced in oe-core or in completely separate
>> layer which would be included only by those who cannot use GPLv3.
>
> Third option would be to reduce the priority of meta-oe to be lower
> than oe-core.
>
> That seems logical regardless of any GPLv3 discussion - since meta-oe
> "fills in the gaps" in oe-core, if something _is_ present in oe-core
> then it probably should be the default version.
>
This scares me: to get a recipe in with old version not supporting
modern file systems you want to change meta-oe's layer priority
risiking unknown issues. I wonder how far the GPLv3 avoidance hype
takes us...

Andreas