From: akuster808 <akuster808@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Robert Yang <liezhi.yang@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] About GPLv2's native recipe
Date: Fri, 23 Jan 2015 09:04:28 -0800 [thread overview]
Message-ID: <54C27F1C.2070606@gmail.com> (raw)
In-Reply-To: <CAP9ODKrqNOqQ1_d7iJRAcpNQgEbeNg=Ve1SLob1m2k2xZX4DkA@mail.gmail.com>
On 01/23/2015 04:47 AM, Otavio Salvador wrote:
> On Fri, Jan 23, 2015 at 12:12 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
>> We have several GPLv2 recipes such as m4-native_1.4.9.bb, while we also
>> have GPLv3's m4-native_1.4.17.bb, I think that we can remove
>> m4-native_1.4.9.bb if the target m4_1.4.9.bb builds well ?
>>
>> I'd like to remove it because we don't build the lower native version by
>> default, and we don't know whether it works or when it would fail.
>
> I second this; not tested recipes are always good to remove.
>
Speaking of not tested, what about 'BLACKLISTED' recipes? is there a
policy regarding how long to keep them around when they are in that state?
- Armin
next prev parent reply other threads:[~2015-01-23 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 2:12 [RFC] About GPLv2's native recipe Robert Yang
2015-01-23 12:47 ` Otavio Salvador
2015-01-23 16:24 ` Christopher Larson
2015-01-23 16:29 ` Otavio Salvador
2015-01-23 17:04 ` akuster808 [this message]
2015-01-23 17:09 ` Paul Eggleton
2015-01-25 21:18 ` Eric Bénard
2015-01-25 22:39 ` Christopher Larson
2015-01-26 1:17 ` Robert Yang
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=54C27F1C.2070606@gmail.com \
--to=akuster808@gmail.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.