From: Tom Rini <tom_rini@mentor.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] ncurses: Update to 5.9
Date: Wed, 6 Apr 2011 10:35:14 -0700 [thread overview]
Message-ID: <4D9CA452.1020205@mentor.com> (raw)
In-Reply-To: <BANLkTimuM8GCHd11cuH5ULA6jL=3kZDk6w@mail.gmail.com>
On 04/06/2011 10:26 AM, Khem Raj wrote:
> On Wed, Apr 6, 2011 at 10:10 AM, Tom Rini <tom_rini@mentor.com> wrote:
>> On 04/06/2011 10:05 AM, Khem Raj wrote:
>>> On Wed, Apr 6, 2011 at 7:30 AM, Tom Rini <tom_rini@mentor.com> wrote:
>>>> On 04/05/2011 11:18 PM, Khem Raj wrote:
>>>>> On Tue, Apr 5, 2011 at 5:38 PM, Tom Rini <tom_rini@mentor.com> wrote:
>>>>>> The previous 5.7 release was relatively close to 5.8 due to it bringing
>>>>>> in a patch to sync with upstream work-in-progress. We skip over the
>>>>>> 5.8 release and move to 5.9.
>>>>>
>>>>>
>>>>> there already are patches for 5.9 available too
>>>>> ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz
>>>>
>>>> Wrong link? That reverse applies to ncurses 5.9 release. But
>>>> regardless, is ncurses something we need to be tracking top of tree for?
>>>> It seems like we needed to for 5.7 since there had been a lot going on
>>>> without a release but that seems to have changed now.
>>>>
>>>
>>> those patches usually contain critical bug fixes including security updates
>>> so it will be of interest to keep track of it
>>
>> Well, it doesn't currently. And while I agree we need to do a good job,
>> everywhere, of keeping track of security updates, I don't think we
>> should move back to depending on a site that frequently removes patches.
>>
>
> yes. cache the patches like yocto did for 5.7 recipes
That still leaves the problem of there not being a valid patch there at
the moment. And I still don't see why ncurses needs to be in the bucket
of recipes we track the scm for rather than relying on the latest stable
release.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-04-06 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 0:37 [PATCH 0/1] Update ncurses Tom Rini
2011-04-06 0:38 ` [PATCH 1/1] ncurses: Update to 5.9 Tom Rini
2011-04-06 6:18 ` Khem Raj
2011-04-06 14:30 ` Tom Rini
2011-04-06 17:05 ` Khem Raj
2011-04-06 17:10 ` Tom Rini
2011-04-06 17:26 ` Khem Raj
2011-04-06 17:35 ` Tom Rini [this message]
2011-04-06 18:27 ` Khem Raj
2011-04-06 18:29 ` Tom Rini
2011-04-06 18:32 ` Khem Raj
2011-04-06 18:48 ` Tom Rini
2011-04-06 20:56 ` Khem Raj
2011-04-06 21:16 ` Richard Purdie
2011-04-07 0:35 ` Tom Rini
2011-04-06 18:38 ` Richard Purdie
2011-04-06 19:20 ` Tom Rini
2011-04-06 20:54 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2011-04-07 0:50 [PATCH 0/1] v2: Update ncurses Tom Rini
2011-04-07 0:50 ` [PATCH 1/1] ncurses: Update to 5.9 Tom Rini
2011-04-08 13:19 ` Richard Purdie
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=4D9CA452.1020205@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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