From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] multilib_header.bbclass: Add oe_multilib_header wrapper
Date: Tue, 26 Jul 2011 10:25:30 -0500 [thread overview]
Message-ID: <4E2EDC6A.50001@windriver.com> (raw)
In-Reply-To: <4E2DA3CB.7070902@windriver.com>
On 7/25/11 12:11 PM, Mark Hatle wrote:
> On 7/25/11 8:54 AM, Phil Blundell wrote:
>> On Mon, 2011-07-25 at 14:47 +0100, Richard Purdie wrote:
>>> +/* Copyright (c) 2005-2011 Wind River Systems, Inc.
>>> + *
>>> + * This program is free software; you can redistribute it and/or modify
>>> + * it under the terms of the GNU Lesser General Public License version 2.1 as
>>> + * published by the Free Software Foundation.
>
> I believe we're flexibly with the license statement in the file.. (Just
> verifying it to make sure I am allowed to change it.)
>
> I personally don't believe it's a big deal, but I understand the concern. Is
> there a different wording/license statement that would make more sense? My
> concern is that if we make the license dynamic it's a lot of pain for no real
> technical reason.
>
> I'd like to see if we (WR) can just put a statement on it that it can be used
> for any purpose -- whatever the legalize is for that -- and if that would
> satisfy your concerns. (BTW: Our goal of course is NOT to change the license of
> the produced binary in any way...)
Looking for feedback, would the CC0:
http://creativecommons.org/publicdomain/zero/1.0/legalcode.txt
work, or would this still "contaminate" the license statement in your opinion?
--Mark
>> This is going to cause LGPL 2.1 content to appear in the output
>> packages. For things like binutils this is probably not a big deal,
>> since they are GPL already, but for ncurses (previously MIT-licensed)
>> this is a potentially significant change. In any case I think there
>> needs to be some way of making sure that the LICENSE is updated
>> appropriately when this file is included.
>>
>> p.
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-07-26 15:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 13:47 [PATCH 0/5] Various multilib related fixes Richard Purdie
2011-07-25 13:47 ` [PATCH 1/5] multilib_header.bbclass: Add oe_multilib_header wrapper Richard Purdie
2011-07-25 13:54 ` Phil Blundell
2011-07-25 17:11 ` Mark Hatle
2011-07-25 20:06 ` Phil Blundell
2011-07-26 15:25 ` Mark Hatle [this message]
2011-07-25 14:35 ` Phil Blundell
2011-07-25 13:47 ` [PATCH 2/5] Fix recipe multilib header conflicts Richard Purdie
2011-07-25 14:08 ` Phil Blundell
2011-07-25 19:11 ` Mark Hatle
2011-07-25 13:47 ` [PATCH 3/5] eglibc: Update 2.13 to avoid multilib conflicts Richard Purdie
2011-07-25 13:59 ` Phil Blundell
2011-07-25 19:04 ` Mark Hatle
2011-07-25 20:04 ` Phil Blundell
2011-07-25 13:47 ` [PATCH 4/5] ncurses: Uncompress man pages Richard Purdie
2011-07-25 14:13 ` Phil Blundell
2011-07-25 19:14 ` Mark Hatle
2011-07-25 14:42 ` Enrico Scholz
2011-07-25 15:28 ` Phil Blundell
2011-07-25 13:47 ` [PATCH 5/5] package.bbclass: fixup_perms - symlink bug fix Richard Purdie
2011-07-25 14:05 ` Phil Blundell
2011-07-25 14:14 ` Enrico Scholz
2011-07-25 14:15 ` Phil Blundell
2011-07-25 19:08 ` Mark Hatle
2011-07-25 19:42 ` Phil Blundell
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=4E2EDC6A.50001@windriver.com \
--to=mark.hatle@windriver.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.