[PATCH 0/1] Update ncurses

[PATCH 0/1] Update ncurses

[Tom Rini]

This updates ncurses to 5.9.  While less of a deal for oe-core where we
had the patch we applied on top of 5.7 mirrored and referenced that
openembedded.master did not and the patch recently went away.  Fortunately
there's now a 5.8 and 5.9 release of ncurses and our 5.7 + patch was
close to 5.8 making this an easy update.

Pull URL: git://git.openembedded.org/openembedded-core-contrib
  Branch: trini/update-ncurses
  Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/update-ncurses

Thanks,
    Tom Rini <tom_rini@mentor.com>
---


Tom Rini (1):
  ncurses: Update to 5.9

 .../{ncurses-5.7 => ncurses-5.9}/config.cache      |    0
 .../{ncurses-5.7 => ncurses-5.9}/tic-hang.patch    |    0
 .../ncurses/{ncurses_5.7.bb => ncurses_5.9.bb}     |   21 +++----------------
 3 files changed, 4 insertions(+), 17 deletions(-)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/config.cache (100%)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/tic-hang.patch (100%)
 rename meta/recipes-core/ncurses/{ncurses_5.7.bb => ncurses_5.9.bb} (88%)

[PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

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.

Signed-off-by: Tom Rini <tom_rini@mentor.com>
---
 .../{ncurses-5.7 => ncurses-5.9}/config.cache      |    0
 .../{ncurses-5.7 => ncurses-5.9}/tic-hang.patch    |    0
 .../ncurses/{ncurses_5.7.bb => ncurses_5.9.bb}     |   21 +++----------------
 3 files changed, 4 insertions(+), 17 deletions(-)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/config.cache (100%)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/tic-hang.patch (100%)
 rename meta/recipes-core/ncurses/{ncurses_5.7.bb => ncurses_5.9.bb} (88%)

diff --git a/meta/recipes-core/ncurses/ncurses-5.7/config.cache b/meta/recipes-core/ncurses/ncurses-5.9/config.cache
similarity index 100%
rename from meta/recipes-core/ncurses/ncurses-5.7/config.cache
rename to meta/recipes-core/ncurses/ncurses-5.9/config.cache
diff --git a/meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch b/meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
similarity index 100%
rename from meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch
rename to meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
diff --git a/meta/recipes-core/ncurses/ncurses_5.7.bb b/meta/recipes-core/ncurses/ncurses_5.9.bb
similarity index 88%
rename from meta/recipes-core/ncurses/ncurses_5.7.bb
rename to meta/recipes-core/ncurses/ncurses_5.9.bb
index 7ab078d..9d4aa22 100644
--- a/meta/recipes-core/ncurses/ncurses_5.7.bb
+++ b/meta/recipes-core/ncurses/ncurses_5.9.bb
@@ -3,34 +3,21 @@ HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cbc180a8c44ca642e97c35452fab5f66"
 SECTION = "libs"
-PATCHDATE = "20100501"
-PKGV = "${PV}+${PATCHDATE}"
-PR = "r1"
+PR = "r0"
 
 DEPENDS = "ncurses-native"
 DEPENDS_virtclass-native = ""
 
 inherit autotools binconfig
 
-SRC_URI = "${GNU_MIRROR}/ncurses/ncurses-${PV}.tar.gz;name=tarball \
-        ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20100424-patch.sh.bz2;apply=yes;name=p20100424sh \
-\
-        http://autobuilder.yoctoproject.org/sources/ncurses-5.7-${PATCHDATE}.patch.gz;name=p20100501 \
+SRC_URI = "${GNU_MIRROR}/ncurses/ncurses-${PV}.tar.gz \
         file://tic-hang.patch \
         file://config.cache \
 "
 
+SRC_URI[md5sum] = "8cb9c412e5f2d96bc6f459aa8c6282a1"
+SRC_URI[sha256sum] = "9046298fb440324c9d4135ecea7879ffed8546dd1b58e59430ea07a4633f563b"
 
-#        ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-${PATCHDATE}.patch.gz;name=p20100501 
-
-SRC_URI[tarball.md5sum] = "cce05daf61a64501ef6cd8da1f727ec6"
-SRC_URI[tarball.sha256sum] = "0a9bdea5c7de8ded5c9327ed642915f2cc380753f12d4ad120ef7da3ea3498f4"
-SRC_URI[p20100424sh.md5sum] = "3a5f76613f0f7ec3e0e73b835bc24864"
-SRC_URI[p20100424sh.sha256sum] = "1e9d70d2d1fe1fea471868832c52f1b9cc6065132102e49e2a3755f2f4f5be53"
-SRC_URI[p20100501.md5sum] = "6518cfa5d45e9069a1e042468161448b"
-SRC_URI[p20100501.sha256sum] = "a97ccc30e4bd6fbb89564f3058db0fe84bd35cfefee831556c500793b477abde"
-
-#PARALLEL_MAKE = ""
 EXTRA_AUTORECONF = "-I m4"
 CONFIG_SITE =+ "${WORKDIR}/config.cache"
 
-- 
1.7.0.4

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

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

>
> Signed-off-by: Tom Rini <tom_rini@mentor.com>
> ---
>  .../{ncurses-5.7 => ncurses-5.9}/config.cache      |    0
>  .../{ncurses-5.7 => ncurses-5.9}/tic-hang.patch    |    0
>  .../ncurses/{ncurses_5.7.bb => ncurses_5.9.bb}     |   21 +++----------------
>  3 files changed, 4 insertions(+), 17 deletions(-)
>  rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/config.cache (100%)
>  rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/tic-hang.patch (100%)
>  rename meta/recipes-core/ncurses/{ncurses_5.7.bb => ncurses_5.9.bb} (88%)
>
> diff --git a/meta/recipes-core/ncurses/ncurses-5.7/config.cache b/meta/recipes-core/ncurses/ncurses-5.9/config.cache
> similarity index 100%
> rename from meta/recipes-core/ncurses/ncurses-5.7/config.cache
> rename to meta/recipes-core/ncurses/ncurses-5.9/config.cache
> diff --git a/meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch b/meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
> similarity index 100%
> rename from meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch
> rename to meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
> diff --git a/meta/recipes-core/ncurses/ncurses_5.7.bb b/meta/recipes-core/ncurses/ncurses_5.9.bb
> similarity index 88%
> rename from meta/recipes-core/ncurses/ncurses_5.7.bb
> rename to meta/recipes-core/ncurses/ncurses_5.9.bb
> index 7ab078d..9d4aa22 100644
> --- a/meta/recipes-core/ncurses/ncurses_5.7.bb
> +++ b/meta/recipes-core/ncurses/ncurses_5.9.bb
> @@ -3,34 +3,21 @@ HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html"
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cbc180a8c44ca642e97c35452fab5f66"
>  SECTION = "libs"
> -PATCHDATE = "20100501"
> -PKGV = "${PV}+${PATCHDATE}"
> -PR = "r1"
> +PR = "r0"
>
>  DEPENDS = "ncurses-native"
>  DEPENDS_virtclass-native = ""
>
>  inherit autotools binconfig
>
> -SRC_URI = "${GNU_MIRROR}/ncurses/ncurses-${PV}.tar.gz;name=tarball \
> -        ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20100424-patch.sh.bz2;apply=yes;name=p20100424sh \
> -\
> -        http://autobuilder.yoctoproject.org/sources/ncurses-5.7-${PATCHDATE}.patch.gz;name=p20100501 \
> +SRC_URI = "${GNU_MIRROR}/ncurses/ncurses-${PV}.tar.gz \
>         file://tic-hang.patch \
>         file://config.cache \
>  "
>
> +SRC_URI[md5sum] = "8cb9c412e5f2d96bc6f459aa8c6282a1"
> +SRC_URI[sha256sum] = "9046298fb440324c9d4135ecea7879ffed8546dd1b58e59430ea07a4633f563b"
>
> -#        ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-${PATCHDATE}.patch.gz;name=p20100501
> -
> -SRC_URI[tarball.md5sum] = "cce05daf61a64501ef6cd8da1f727ec6"
> -SRC_URI[tarball.sha256sum] = "0a9bdea5c7de8ded5c9327ed642915f2cc380753f12d4ad120ef7da3ea3498f4"
> -SRC_URI[p20100424sh.md5sum] = "3a5f76613f0f7ec3e0e73b835bc24864"
> -SRC_URI[p20100424sh.sha256sum] = "1e9d70d2d1fe1fea471868832c52f1b9cc6065132102e49e2a3755f2f4f5be53"
> -SRC_URI[p20100501.md5sum] = "6518cfa5d45e9069a1e042468161448b"
> -SRC_URI[p20100501.sha256sum] = "a97ccc30e4bd6fbb89564f3058db0fe84bd35cfefee831556c500793b477abde"
> -
> -#PARALLEL_MAKE = ""
>  EXTRA_AUTORECONF = "-I m4"
>  CONFIG_SITE =+ "${WORKDIR}/config.cache"
>
> --
> 1.7.0.4
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

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.

-- 
Tom Rini
Mentor Graphics Corporation

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

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

> --
> Tom Rini
> Mentor Graphics Corporation
>

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

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.

-- 
Tom Rini
Mentor Graphics Corporation

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

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
> --
> Tom Rini
> Mentor Graphics Corporation
>

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

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

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

On Wed, Apr 6, 2011 at 10:35 AM, Tom Rini <tom_rini@mentor.com> wrote:
> 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.
>

5.9 was released few days back so that patch might be lean for now
but I assume overtime it will get fatter

> --
> Tom Rini
> Mentor Graphics Corporation
>

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

On 04/06/2011 11:27 AM, Khem Raj wrote:
> On Wed, Apr 6, 2011 at 10:35 AM, Tom Rini <tom_rini@mentor.com> wrote:
>> 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.
> 
> 5.9 was released few days back so that patch might be lean for now
> but I assume overtime it will get fatter

It's invalid at the moment, yes.  But you haven't explained why ncurses
needs to be in the bleeding edge bucket.  Usually this is for stuff that
hasn't really reached a stability point.

-- 
Tom Rini
Mentor Graphics Corporation

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

On Wed, Apr 6, 2011 at 11:29 AM, Tom Rini <tom_rini@mentor.com> wrote:
> On 04/06/2011 11:27 AM, Khem Raj wrote:
>> On Wed, Apr 6, 2011 at 10:35 AM, Tom Rini <tom_rini@mentor.com> wrote:
>>> 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.
>>
>> 5.9 was released few days back so that patch might be lean for now
>> but I assume overtime it will get fatter
>
> It's invalid at the moment, yes.  But you haven't explained why ncurses
> needs to be in the bleeding edge bucket.  Usually this is for stuff that
> hasn't really reached a stability point.
>
It does not have to be but those patches are cumulative fixed that are done
on top of a release. I am sure we will also run into the problems those will
fix thats why its better to keep and eye on them
> --
> Tom Rini
> Mentor Graphics Corporation
>

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

On 04/06/2011 11:32 AM, Khem Raj wrote:
> On Wed, Apr 6, 2011 at 11:29 AM, Tom Rini <tom_rini@mentor.com> wrote:
>> On 04/06/2011 11:27 AM, Khem Raj wrote:
>>> On Wed, Apr 6, 2011 at 10:35 AM, Tom Rini <tom_rini@mentor.com> wrote:
>>>> 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.
>>>
>>> 5.9 was released few days back so that patch might be lean for now
>>> but I assume overtime it will get fatter
>>
>> It's invalid at the moment, yes.  But you haven't explained why ncurses
>> needs to be in the bleeding edge bucket.  Usually this is for stuff that
>> hasn't really reached a stability point.
>>
> It does not have to be but those patches are cumulative fixed that are done
> on top of a release. I am sure we will also run into the problems those will
> fix thats why its better to keep and eye on them

That can be said for just about every recipe we have.  It sounds like
you're suggesting we need _svn recipe or similar recipe for ncurses as
well.  I still don't see why ncurses is special in this regard and ask
that when you see a worthwhile patch for ncurses 5.9 that you do another
pull request.  I'm just trying to keep oe-core in sync with
openembedded.master.

-- 
Tom Rini
Mentor Graphics Corporation

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

On Wed, Apr 6, 2011 at 11:48 AM, Tom Rini <tom_rini@mentor.com> wrote:
> On 04/06/2011 11:32 AM, Khem Raj wrote:
>> On Wed, Apr 6, 2011 at 11:29 AM, Tom Rini <tom_rini@mentor.com> wrote:
>>> On 04/06/2011 11:27 AM, Khem Raj wrote:
>>>> On Wed, Apr 6, 2011 at 10:35 AM, Tom Rini <tom_rini@mentor.com> wrote:
>>>>> 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.
>>>>
>>>> 5.9 was released few days back so that patch might be lean for now
>>>> but I assume overtime it will get fatter
>>>
>>> It's invalid at the moment, yes.  But you haven't explained why ncurses
>>> needs to be in the bleeding edge bucket.  Usually this is for stuff that
>>> hasn't really reached a stability point.
>>>
>> It does not have to be but those patches are cumulative fixed that are done
>> on top of a release. I am sure we will also run into the problems those will
>> fix thats why its better to keep and eye on them
>
> That can be said for just about every recipe we have.  It sounds like
> you're suggesting we need _svn recipe or similar recipe for ncurses as
> well.  I still don't see why ncurses is special in this regard and ask
> that when you see a worthwhile patch for ncurses 5.9 that you do another
> pull request.  I'm just trying to keep oe-core in sync with
> openembedded.master.
>

Those patches are not same as all patches that would be applied to say
svn version these are fixes on top of a release e.g. 5.9 I was merely
suggesting that your upgrade patch is fine please see if there already
are some fixes on top of 5.9 that we need
thats all


> --
> Tom Rini
> Mentor Graphics Corporation
>

Re: [PATCH 1/1] ncurses: Update to 5.9

[Richard Purdie]

On Wed, 2011-04-06 at 10:35 -0700, Tom Rini wrote:
> 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.

It sounds like these patches are more like tracking an SCM rather than a
source of specific security patches or critical updates.

I think it might be wise to note this location in the recipe as a
comment (can someone please send an updated patch) but I don't think we
should be including these patches by default, particular if upstream are
making regular releases again.

Cheers,

Richard

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

On 04/06/2011 02:16 PM, Richard Purdie wrote:
> On Wed, 2011-04-06 at 10:35 -0700, Tom Rini wrote:
>> 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.
> 
> It sounds like these patches are more like tracking an SCM rather than a
> source of specific security patches or critical updates.
> 
> I think it might be wise to note this location in the recipe as a
> comment (can someone please send an updated patch) but I don't think we
> should be including these patches by default, particular if upstream are
> making regular releases again.

I'll go v2 it

-- 
Tom Rini
Mentor Graphics Corporation

Re: [PATCH 1/1] ncurses: Update to 5.9

[Richard Purdie]

On Tue, 2011-04-05 at 23:18 -0700, 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

Can someone summarise what the benefits of these patches are? I'm
trying to figure out whether we lose anything due to this upgrade or
not...

Cheers,

Richard

Re: [PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

On 04/06/2011 11:38 AM, Richard Purdie wrote:
> On Tue, 2011-04-05 at 23:18 -0700, 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
> 
> Can someone summarise what the benefits of these patches are? I'm
> trying to figure out whether we lose anything due to this upgrade or
> not...

The patches we applied to 5.7 are part of the 5.8 release and 5.9 of
course replaces 5.8.  The invisible-island.net patch sets are things
taken from the official source repo and put out there for use.

-- 
Tom Rini
Mentor Graphics Corporation

Re: [PATCH 1/1] ncurses: Update to 5.9

[Khem Raj]

On Wed, Apr 6, 2011 at 11:38 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2011-04-05 at 23:18 -0700, 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
>
> Can someone summarise what the benefits of these patches are? I'm
> trying to figure out whether we lose anything due to this upgrade or
> not...
>

ftp://invisible-island.net/ncurses/5.9/README

> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

[PATCH 0/1] v2: Update ncurses

[Tom Rini]

This updates ncurses to 5.9.  While less of a deal for oe-core where we
had the patch we applied on top of 5.7 mirrored and referenced that
openembedded.master did not and the patch recently went away.  Fortunately
there's now a 5.8 and 5.9 release of ncurses and our 5.7 + patch was
close to 5.8 making this an easy update.  While at this we move most of
the important parts of ncurses_5.x.bb into ncurses.inc which has previously
been unused.  Finally, we add a comment saying that invisible-island.net
may have useful additional patches.

Pull URL: git://git.openembedded.org/openembedded-core-contrib
  Branch: trini/update-ncurses
  Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/update-ncurses

Thanks,
    Tom Rini <tom_rini@mentor.com>
---


Tom Rini (1):
  ncurses: Update to 5.9

 .../{ncurses-5.7 => ncurses-5.9}/config.cache      |    0
 .../{ncurses-5.7 => ncurses-5.9}/tic-hang.patch    |    0
 meta/recipes-core/ncurses/ncurses.inc              |  256 +++++++++++++++-----
 meta/recipes-core/ncurses/ncurses_5.7.bb           |  246 -------------------
 meta/recipes-core/ncurses/ncurses_5.9.bb           |   10 +
 5 files changed, 204 insertions(+), 308 deletions(-)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/config.cache (100%)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/tic-hang.patch (100%)
 delete mode 100644 meta/recipes-core/ncurses/ncurses_5.7.bb
 create mode 100644 meta/recipes-core/ncurses/ncurses_5.9.bb

[PATCH 1/1] ncurses: Update to 5.9

[Tom Rini]

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.  Also, we move most of the contents of the
main recipe into the previously unused ncurses.inc file.

Signed-off-by: Tom Rini <tom_rini@mentor.com>
---
 .../{ncurses-5.7 => ncurses-5.9}/config.cache      |    0
 .../{ncurses-5.7 => ncurses-5.9}/tic-hang.patch    |    0
 meta/recipes-core/ncurses/ncurses.inc              |  256 +++++++++++++++-----
 meta/recipes-core/ncurses/ncurses_5.7.bb           |  246 -------------------
 meta/recipes-core/ncurses/ncurses_5.9.bb           |   10 +
 5 files changed, 204 insertions(+), 308 deletions(-)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/config.cache (100%)
 rename meta/recipes-core/ncurses/{ncurses-5.7 => ncurses-5.9}/tic-hang.patch (100%)
 delete mode 100644 meta/recipes-core/ncurses/ncurses_5.7.bb
 create mode 100644 meta/recipes-core/ncurses/ncurses_5.9.bb

diff --git a/meta/recipes-core/ncurses/ncurses-5.7/config.cache b/meta/recipes-core/ncurses/ncurses-5.9/config.cache
similarity index 100%
rename from meta/recipes-core/ncurses/ncurses-5.7/config.cache
rename to meta/recipes-core/ncurses/ncurses-5.9/config.cache
diff --git a/meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch b/meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
similarity index 100%
rename from meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch
rename to meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch
diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
index 3f897f6..e244eb8 100644
--- a/meta/recipes-core/ncurses/ncurses.inc
+++ b/meta/recipes-core/ncurses/ncurses.inc
@@ -2,7 +2,7 @@ SUMMARY = "The New Curses library"
 DESCRIPTION = "SVr4 and XSI-Curses compatible curses library and terminfo tools including tic, infocmp, captoinfo. Supports color, multiple highlights, forms-drawing characters, and automatic recognition of keypad and function-key sequences. Extensions include resizable windows and mouse support on both xterm and Linux console using the gpm library."
 HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html"
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cf3c7ab00720a1b83391f49ea9956277"
+LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cbc180a8c44ca642e97c35452fab5f66"
 SECTION = "libs"
 DEPENDS = "ncurses-native"
 DEPENDS_virtclass-native = ""
@@ -11,53 +11,121 @@ PACKAGES_append = " ncurses-terminfo"
 FILES_ncurses_append = " ${datadir}/tabset"
 RSUGGESTS_${PN} = "ncurses-terminfo"
 RPROVIDES = "libncurses5"
+INC_PR = "r0"
 
-inherit autotools
+inherit autotools binconfig
 
-# This keeps only tput/tset in ncurses
-# clear/reset are in already busybox
-FILES_ncurses-tools = "${bindir}/tic ${bindir}/toe ${bindir}/infotocap ${bindir}/captoinfo ${bindir}/infocmp ${bindir}/clear.${PN} ${bindir}/reset.${PN} ${bindir}/tack "
-FILES_ncurses-terminfo = "${datadir}/terminfo"
-FILES_${PN} = "${bindir}/tput ${bindir}/tset ${libdir}/lib*.so.* /usr/share/tabset /etc/terminfo"
-
-PARALLEL_MAKE=""
-
-FILESPATH = "${FILE_DIRNAME}/local:${FILE_DIRNAME}/ncurses-${PV}-${PR}:${FILE_DIRNAME}/ncurses-${PV}:${FILE_DIRNAME}/ncurses:${FILE_DIRNAME}"
-
-EXTRA_OECONF = "--with-shared \
-                --with-libtool \
-	        --without-profile \
-	        --without-debug \
-	        --disable-rpath \
-	        --enable-echo \
-	        --enable-const \
-	        --without-ada \
-	        --enable-termcap \
-	        --without-cxx-binding \
-	        --with-terminfo-dirs=${sysconfdir}/terminfo:${datadir}/terminfo \
-	        --enable-overwrite \
-	        --with-build-ldflags='' \
-	        --with-build-ccflags='' "
-export BUILD_CCFLAGS = "-I${S}/ncurses -I${S}/include ${BUILD_CFLAGS}"
-export BUILD_LDFLAGS = ""
-export EXTRA_OEMAKE = '"BUILD_LDFLAGS=" "BUILD_CCFLAGS=${BUILD_CCFLAGS}"'
+# Upstream has useful patches at times at ftp://invisible-island.net/ncurses/
+SRC_URI = "${GNU_MIRROR}/ncurses/ncurses-${PV}.tar.gz"
+
+EXTRA_AUTORECONF = "-I m4"
+CONFIG_SITE =+ "${WORKDIR}/config.cache"
+
+# Whether to enable separate widec libraries; must be 'true' or 'false'
+#
+# TODO: remove this variable when widec is supported in every setup?
+ENABLE_WIDEC = "true"
+
+# _GNU_SOURCE is required for widec stuff and is detected automatically
+# for target objects.  But it must be set manually for native and sdk
+# builds.
+BUILD_CPPFLAGS += "-D_GNU_SOURCE"
+
+# Override the function from the autotools class; ncurses requires a
+# patched autoconf213 to generate the configure script. This autoconf
+# is not available so that the shipped script will be used.
+do_configure() {
+        # check does not work with cross-compiling and is generally
+        # broken because it requires stdin to be pollable (which is
+        # not the case for /dev/null redirections)
+        export cf_cv_working_poll=yes
+
+        for i in \
+        'narrowc' \
+        'widec   --enable-widec --without-progs'; do
+                set -- $i
+                mkdir -p $1
+                cd $1
+                shift
+
+                oe_runconf \
+                        --disable-static \
+                        --without-debug \
+                        --without-ada \
+                        --without-gpm \
+                        --enable-hard-tabs \
+                        --enable-xmc-glitch \
+                        --enable-colorfgbg \
+                        --with-termpath='${sysconfdir}/termcap:${datadir}/misc/termcap' \
+                        --with-terminfo-dirs='${sysconfdir}/terminfo:${datadir}/terminfo' \
+                        --with-shared \
+                        --disable-big-core \
+                        --program-prefix= \
+                        --with-ticlib \
+                        --with-termlib=tinfo \
+                        --enable-sigwinch \
+                        --enable-pc-files \
+                        --disable-rpath-hack \
+                        "$@"
+                cd ..
+        done
+}
+
+do_compile() {
+        oe_runmake -C narrowc libs
+        oe_runmake -C narrowc/progs
+
+        ! ${ENABLE_WIDEC} || \
+            oe_runmake -C widec libs
+}
+
+# set of expected differences between narrowc and widec header
+#
+# TODO: the NCURSES_CH_T difference can cause real problems :(
+_unifdef_cleanup = " \
+  -e '\!/\* \$Id: curses.wide,v!,\!/\* \$Id: curses.tail,v!d' \
+  -e '/^#define NCURSES_CH_T /d' \
+  -e '/^#include <wchar.h>/d' \
+  -e '\!^/\* .* \*/!d' \
+"
+
+do_test[depends] = "unifdef-native:do_populate_sysroot"
+do_test[dirs] = "${S}"
+do_test() {
+        ${ENABLE_WIDEC} || return 0
+
+        # make sure that the narrow and widec header are compatible
+        # and differ only in minor details.
+        unifdef -k narrowc/include/curses.h | \
+            sed ${_unifdef_cleanup} > curses-narrowc.h
+        unifdef -k widec/include/curses.h | \
+            sed ${_unifdef_cleanup} > curses-widec.h
+
+        diff curses-narrowc.h curses-widec.h
+}
+
+_install_opts = "\
+  DESTDIR='${D}' \
+  PKG_CONFIG_LIBDIR='${libdir}/pkgconfig' \
+  install.libs install.includes install.man \
+"
 
 do_install() {
-	# This is necessary so that the "tic" command executed during the install can
-	# link with the correct libary in staging.
-	export LD_LIBRARY_PATH="${STAGING_LIBDIR_NATIVE}"
+        # Order of installation is important; widec installs a 'curses.h'
+        # header with more definitions and must be installed last hence.
+        # Compatibility of these headers will be checked in 'do_test()'.
+        oe_runmake -C narrowc ${_install_opts} \
+                install.data install.progs
 
-	autotools_do_install
+        ! ${ENABLE_WIDEC} || \
+            oe_runmake -C widec ${_install_opts}
 
-	ln -sf curses.h ${D}${includedir}/ncurses.h
 
-	# our ncurses has termcap support
-	ln -sf libncurses.so ${D}${libdir}/libtermcap.so
-	ln -sf libncurses.a ${D}${libdir}/libtermcap.a
+        cd narrowc
 
-	# include some basic terminfo files
-	# stolen ;) from gentoo and modified a bit
-	for x in ansi console dumb linux rxvt screen sun vt{52,100,102,200,220} xterm-color xterm-xfree86
+        # include some basic terminfo files
+        # stolen ;) from gentoo and modified a bit
+        for x in ansi console dumb linux rxvt screen sun vt{52,100,102,200,220} xterm-color xterm-xfree86
         do
                 local termfile="$(find "${D}${datadir}/terminfo/" -name "${x}" 2>/dev/null)"
                 local basedir="$(basename $(dirname "${termfile}"))"
@@ -70,32 +138,96 @@ do_install() {
                                 ${D}${datadir}/terminfo/${basedir}/${x}
                 fi
         done
-	# i think we can use xterm-color as default xterm
-	if [ -e ${D}${sysconfdir}/terminfo/x/xterm-color ]
-	then
-		ln -sf xterm-color ${D}${sysconfdir}/terminfo/x/xterm
-	fi
-
-	if [ "${PN}" = "ncurses" ]; then
-		mv ${D}${bindir}/clear ${D}${bindir}/clear.${PN}
-		mv ${D}${bindir}/reset ${D}${bindir}/reset.${PN}
-	fi
+        # i think we can use xterm-color as default xterm
+        if [ -e ${D}${sysconfdir}/terminfo/x/xterm-color ]
+        then
+                ln -sf xterm-color ${D}${sysconfdir}/terminfo/x/xterm
+        fi
+
+        if [ "${PN}" = "ncurses" ]; then
+                mv ${D}${bindir}/clear ${D}${bindir}/clear.${PN}
+                mv ${D}${bindir}/reset ${D}${bindir}/reset.${PN}
+        fi
+
+
+        # create linker scripts for libcurses.so and libncurses to
+        # link against -ltinfo when needed. Some builds might break
+        # else when '-Wl,--no-copy-dt-needed-entries' has been set in
+        # linker flags.
+        for i in libncurses libncursesw; do
+		f=${D}${libdir}/$i.so
+                test -h $f || continue
+                rm -f $f
+                echo '/* GNU ld script */'  >$f
+                echo "INPUT($i.so.5 AS_NEEDED(-ltinfo))" >>$f
+        done
+
+        # create libtermcap.so linker script for backward compatibility
+        f=${D}${libdir}/libtermcap.so
+        echo '/* GNU ld script */' >$f
+        echo 'INPUT(AS_NEEDED(-ltinfo))' >>$f
 }
-		
-		
+
+python populate_packages_prepend () {
+        libdir = bb.data.expand("${libdir}", d)
+        pnbase = bb.data.expand("${PN}-lib%s", d)
+        do_split_packages(d, libdir, '^lib(.*)\.so\..*', pnbase, 'ncurses %s library', prepend=True, extra_depends = '', allow_links=True)
+}
+
+
 pkg_postinst_ncurses-tools () {
-	if [ "${PN}" = "ncurses" ]; then
-		update-alternatives --install ${bindir}/clear clear clear.${PN} 100
-		update-alternatives --install ${bindir}/reset reset reset.${PN} 100
-	fi
+        if [ "${PN}" = "ncurses" ]; then
+                update-alternatives --install ${bindir}/clear clear clear.${PN} 100
+                update-alternatives --install ${bindir}/reset reset reset.${PN} 100
+        fi
 }
-				
-			
+
 pkg_prerm_ncurses-tools () {
-	if [ "${PN}" = "ncurses" ]; then
-		update-alternatives --remove clear clear.${PN}
-		update-alternatives --remove reset reset.${PN}
-	fi
+        if [ "${PN}" = "ncurses" ]; then
+                update-alternatives --remove clear clear.${PN}
+                update-alternatives --remove reset reset.${PN}
+        fi
 }
 
 BBCLASSEXTEND = "native nativesdk"
+
+PACKAGES += " \
+  ${PN}-tools \
+  ${PN}-terminfo \
+  ${PN}-terminfo-base \
+"
+
+FILES_${PN} = "\
+  ${bindir}/tput \
+  ${bindir}/tset \
+  ${bindir}/ncurses5-config \
+  ${bindir}/ncursesw5-config \
+  ${datadir}/tabset \
+"
+
+# This keeps only tput/tset in ncurses
+# clear/reset are in already busybox
+FILES_${PN}-tools = "\
+  ${bindir}/tic \
+  ${bindir}/toe \
+  ${bindir}/infotocap \
+  ${bindir}/captoinfo \
+  ${bindir}/infocmp \
+  ${bindir}/clear.${PN} \
+  ${bindir}/reset.${PN} \
+  ${bindir}/tack \
+  ${bindir}/tabs \
+"
+# 'reset' is a symlink to 'tset' which is in the 'ncurses' package
+RDEPENDS_${PN}-tools = "${PN}"
+
+FILES_${PN}-terminfo = "\
+  ${datadir}/terminfo \
+"
+
+FILES_${PN}-terminfo-base = "\
+  ${sysconfdir}/terminfo \
+"
+
+RSUGGESTS_${PN}-libtinfo = "${PN}-terminfo"
+RRECOMMENDS_${PN}-libtinfo = "${PN}-terminfo-base"
diff --git a/meta/recipes-core/ncurses/ncurses_5.7.bb b/meta/recipes-core/ncurses/ncurses_5.7.bb
deleted file mode 100644
index 7ab078d..0000000
--- a/meta/recipes-core/ncurses/ncurses_5.7.bb
+++ /dev/null
@@ -1,246 +0,0 @@
-DESCRIPTION = "Ncurses library"
-HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html"
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://ncurses/base/version.c;beginline=1;endline=27;md5=cbc180a8c44ca642e97c35452fab5f66"
-SECTION = "libs"
-PATCHDATE = "20100501"
-PKGV = "${PV}+${PATCHDATE}"
-PR = "r1"
-
-DEPENDS = "ncurses-native"
-DEPENDS_virtclass-native = ""
-
-inherit autotools binconfig
-
-SRC_URI = "${GNU_MIRROR}/ncurses/ncurses-${PV}.tar.gz;name=tarball \
-        ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-20100424-patch.sh.bz2;apply=yes;name=p20100424sh \
-\
-        http://autobuilder.yoctoproject.org/sources/ncurses-5.7-${PATCHDATE}.patch.gz;name=p20100501 \
-        file://tic-hang.patch \
-        file://config.cache \
-"
-
-
-#        ftp://invisible-island.net/ncurses/5.7/ncurses-5.7-${PATCHDATE}.patch.gz;name=p20100501 
-
-SRC_URI[tarball.md5sum] = "cce05daf61a64501ef6cd8da1f727ec6"
-SRC_URI[tarball.sha256sum] = "0a9bdea5c7de8ded5c9327ed642915f2cc380753f12d4ad120ef7da3ea3498f4"
-SRC_URI[p20100424sh.md5sum] = "3a5f76613f0f7ec3e0e73b835bc24864"
-SRC_URI[p20100424sh.sha256sum] = "1e9d70d2d1fe1fea471868832c52f1b9cc6065132102e49e2a3755f2f4f5be53"
-SRC_URI[p20100501.md5sum] = "6518cfa5d45e9069a1e042468161448b"
-SRC_URI[p20100501.sha256sum] = "a97ccc30e4bd6fbb89564f3058db0fe84bd35cfefee831556c500793b477abde"
-
-#PARALLEL_MAKE = ""
-EXTRA_AUTORECONF = "-I m4"
-CONFIG_SITE =+ "${WORKDIR}/config.cache"
-
-# Whether to enable separate widec libraries; must be 'true' or 'false'
-#
-# TODO: remove this variable when widec is supported in every setup?
-ENABLE_WIDEC = "true"
-
-# _GNU_SOURCE is required for widec stuff and is detected automatically
-# for target objects.  But it must be set manually for native and sdk
-# builds.
-BUILD_CPPFLAGS += "-D_GNU_SOURCE"
-
-# Override the function from the autotools class; ncurses requires a
-# patched autoconf213 to generate the configure script. This autoconf
-# is not available so that the shipped script will be used.
-do_configure() {
-        # check does not work with cross-compiling and is generally
-        # broken because it requires stdin to be pollable (which is
-        # not the case for /dev/null redirections)
-        export cf_cv_working_poll=yes
-
-        for i in \
-        'narrowc' \
-        'widec   --enable-widec --without-progs'; do
-                set -- $i
-                mkdir -p $1
-                cd $1
-                shift
-
-                oe_runconf \
-                        --disable-static \
-                        --without-debug \
-                        --without-ada \
-                        --without-gpm \
-                        --enable-hard-tabs \
-                        --enable-xmc-glitch \
-                        --enable-colorfgbg \
-                        --with-termpath='${sysconfdir}/termcap:${datadir}/misc/termcap' \
-                        --with-terminfo-dirs='${sysconfdir}/terminfo:${datadir}/terminfo' \
-                        --with-shared \
-                        --disable-big-core \
-                        --program-prefix= \
-                        --with-ticlib \
-                        --with-termlib=tinfo \
-                        --enable-sigwinch \
-                        --enable-pc-files \
-                        --disable-rpath-hack \
-                        "$@"
-                cd ..
-        done
-}
-
-do_compile() {
-        oe_runmake -C narrowc libs
-        oe_runmake -C narrowc/progs
-
-        ! ${ENABLE_WIDEC} || \
-            oe_runmake -C widec libs
-}
-
-# set of expected differences between narrowc and widec header
-#
-# TODO: the NCURSES_CH_T difference can cause real problems :(
-_unifdef_cleanup = " \
-  -e '\!/\* \$Id: curses.wide,v!,\!/\* \$Id: curses.tail,v!d' \
-  -e '/^#define NCURSES_CH_T /d' \
-  -e '/^#include <wchar.h>/d' \
-  -e '\!^/\* .* \*/!d' \
-"
-
-do_test[depends] = "unifdef-native:do_populate_sysroot"
-do_test[dirs] = "${S}"
-do_test() {
-        ${ENABLE_WIDEC} || return 0
-
-        # make sure that the narrow and widec header are compatible
-        # and differ only in minor details.
-        unifdef -k narrowc/include/curses.h | \
-            sed ${_unifdef_cleanup} > curses-narrowc.h
-        unifdef -k widec/include/curses.h | \
-            sed ${_unifdef_cleanup} > curses-widec.h
-
-        diff curses-narrowc.h curses-widec.h
-}
-
-_install_opts = "\
-  DESTDIR='${D}' \
-  PKG_CONFIG_LIBDIR='${libdir}/pkgconfig' \
-  install.libs install.includes install.man \
-"
-
-do_install() {
-        # Order of installation is important; widec installs a 'curses.h'
-        # header with more definitions and must be installed last hence.
-        # Compatibility of these headers will be checked in 'do_test()'.
-        oe_runmake -C narrowc ${_install_opts} \
-                install.data install.progs
-
-        ! ${ENABLE_WIDEC} || \
-            oe_runmake -C widec ${_install_opts}
-
-
-        cd narrowc
-
-        # include some basic terminfo files
-        # stolen ;) from gentoo and modified a bit
-        for x in ansi console dumb linux rxvt screen sun vt{52,100,102,200,220} xterm-color xterm-xfree86
-        do
-                local termfile="$(find "${D}${datadir}/terminfo/" -name "${x}" 2>/dev/null)"
-                local basedir="$(basename $(dirname "${termfile}"))"
-
-                if [ -n "${termfile}" ]
-                then
-                        install -d ${D}${sysconfdir}/terminfo/${basedir}
-                        mv ${termfile} ${D}${sysconfdir}/terminfo/${basedir}/
-                        ln -s /etc/terminfo/${basedir}/${x} \
-                                ${D}${datadir}/terminfo/${basedir}/${x}
-                fi
-        done
-        # i think we can use xterm-color as default xterm
-        if [ -e ${D}${sysconfdir}/terminfo/x/xterm-color ]
-        then
-                ln -sf xterm-color ${D}${sysconfdir}/terminfo/x/xterm
-        fi
-
-        if [ "${PN}" = "ncurses" ]; then
-                mv ${D}${bindir}/clear ${D}${bindir}/clear.${PN}
-                mv ${D}${bindir}/reset ${D}${bindir}/reset.${PN}
-        fi
-
-
-        # create linker scripts for libcurses.so and libncurses to
-        # link against -ltinfo when needed. Some builds might break
-        # else when '-Wl,--no-copy-dt-needed-entries' has been set in
-        # linker flags.
-        for i in libncurses libncursesw; do
-		f=${D}${libdir}/$i.so
-                test -h $f || continue
-                rm -f $f
-                echo '/* GNU ld script */'  >$f
-                echo "INPUT($i.so.5 AS_NEEDED(-ltinfo))" >>$f
-        done
-
-        # create libtermcap.so linker script for backward compatibility
-        f=${D}${libdir}/libtermcap.so
-        echo '/* GNU ld script */' >$f
-        echo 'INPUT(AS_NEEDED(-ltinfo))' >>$f
-}
-
-python populate_packages_prepend () {
-        libdir = bb.data.expand("${libdir}", d)
-        pnbase = bb.data.expand("${PN}-lib%s", d)
-        do_split_packages(d, libdir, '^lib(.*)\.so\..*', pnbase, 'ncurses %s library', prepend=True, extra_depends = '', allow_links=True)
-}
-
-
-pkg_postinst_ncurses-tools () {
-        if [ "${PN}" = "ncurses" ]; then
-                update-alternatives --install ${bindir}/clear clear clear.${PN} 100
-                update-alternatives --install ${bindir}/reset reset reset.${PN} 100
-        fi
-}
-
-pkg_prerm_ncurses-tools () {
-        if [ "${PN}" = "ncurses" ]; then
-                update-alternatives --remove clear clear.${PN}
-                update-alternatives --remove reset reset.${PN}
-        fi
-}
-
-BBCLASSEXTEND = "native nativesdk"
-
-PACKAGES += " \
-  ${PN}-tools \
-  ${PN}-terminfo \
-  ${PN}-terminfo-base \
-"
-
-FILES_${PN} = "\
-  ${bindir}/tput \
-  ${bindir}/tset \
-  ${bindir}/ncurses5-config \
-  ${bindir}/ncursesw5-config \
-  ${datadir}/tabset \
-"
-
-# This keeps only tput/tset in ncurses
-# clear/reset are in already busybox
-FILES_${PN}-tools = "\
-  ${bindir}/tic \
-  ${bindir}/toe \
-  ${bindir}/infotocap \
-  ${bindir}/captoinfo \
-  ${bindir}/infocmp \
-  ${bindir}/clear.${PN} \
-  ${bindir}/reset.${PN} \
-  ${bindir}/tack \
-  ${bindir}/tabs \
-"
-# 'reset' is a symlink to 'tset' which is in the 'ncurses' package
-RDEPENDS_${PN}-tools = "${PN}"
-
-FILES_${PN}-terminfo = "\
-  ${datadir}/terminfo \
-"
-
-FILES_${PN}-terminfo-base = "\
-  ${sysconfdir}/terminfo \
-"
-
-RSUGGESTS_${PN}-libtinfo = "${PN}-terminfo"
-RRECOMMENDS_${PN}-libtinfo = "${PN}-terminfo-base"
diff --git a/meta/recipes-core/ncurses/ncurses_5.9.bb b/meta/recipes-core/ncurses/ncurses_5.9.bb
new file mode 100644
index 0000000..4e1f143
--- /dev/null
+++ b/meta/recipes-core/ncurses/ncurses_5.9.bb
@@ -0,0 +1,10 @@
+require ncurses.inc
+
+PR = "${INC_PR}.0"
+
+SRC_URI += "file://tic-hang.patch \
+            file://config.cache \
+"
+
+SRC_URI[md5sum] = "8cb9c412e5f2d96bc6f459aa8c6282a1"
+SRC_URI[sha256sum] = "9046298fb440324c9d4135ecea7879ffed8546dd1b58e59430ea07a4633f563b"
-- 
1.7.0.4

Re: [PATCH 1/1] ncurses: Update to 5.9

[Richard Purdie]

On Wed, 2011-04-06 at 17:50 -0700, Tom Rini 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.  Also, we move most of the contents of the
> main recipe into the previously unused ncurses.inc file.
> 
> Signed-off-by: Tom Rini <tom_rini@mentor.com>

Merged to master although in future if you're going to move large chunks
of the files around, I think it would look better as two commits as its
hard to tell what changed and what just moved.

Cheers,

Richard