Update ncurses

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 <[email protected]>

---
 .../{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%)

meta/recipes-core/ncurses/ncurses-5.9/config.cache renamed from meta/recipes-core/ncurses/ncurses-5.7/config.cache +0 -0

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

meta/recipes-core/ncurses/ncurses-5.9/tic-hang.patch renamed from meta/recipes-core/ncurses/ncurses-5.7/tic-hang.patch +0 -0

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

meta/recipes-core/ncurses/ncurses_5.9.bb renamed from meta/recipes-core/ncurses/ncurses_5.7.bb +0 -0

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
@@ -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"

meta/recipes-core/ncurses/ncurses_5.9.bb renamed from meta/recipes-core/ncurses/ncurses_5.7.bb +1 -3

-PATCHDATE = "20100501"
-PKGV = "${PV}+${PATCHDATE}"
-PR = "r1"
+PR = "r0"

 DEPENDS = "ncurses-native"
 DEPENDS_virtclass-native = ""

 inherit autotools binconfig

meta/recipes-core/ncurses/ncurses_5.9.bb renamed from meta/recipes-core/ncurses/ncurses_5.7.bb +1 -4

-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 \
 "

meta/recipes-core/ncurses/ncurses_5.9.bb renamed from meta/recipes-core/ncurses/ncurses_5.7.bb +2 -10

+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
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 6 lines · Khem Raj

Quoted 3 lines · 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.

Quoted 2 lines

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

Quoted 10 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 5 lines

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

Quoted 17 lines · Khem Raj

Quoted 15 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

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.

Quoted 2 lines

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

Quoted 21 lines · Tom Rini

Quoted 19 lines · Khem Raj

Quoted 7 lines · Tom Rini

Quoted 6 lines · Khem Raj

Quoted 3 lines · 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.

Quoted 8 lines

Quoted 2 lines

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

Quoted 4 lines

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

Quoted 27 lines · Khem Raj

Quoted 25 lines · Tom Rini

Quoted 11 lines · Khem Raj

Quoted 10 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 8 lines

Quoted 5 lines

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.

Quoted 1 line

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

Quoted 30 lines · Tom Rini

Quoted 28 lines · Khem Raj

Quoted 18 lines · Tom Rini

Quoted 17 lines · Khem Raj

Quoted 15 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

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.

Quoted 7 lines

Quoted 2 lines

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

Quoted 4 lines

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

Quoted 36 lines · Khem Raj

Quoted 34 lines · Tom Rini

Quoted 22 lines · Khem Raj

Quoted 21 lines · Tom Rini

Quoted 19 lines · Khem Raj

Quoted 7 lines · Tom Rini

Quoted 6 lines · Khem Raj

Quoted 3 lines · 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.

Quoted 8 lines

Quoted 2 lines

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

Quoted 6 lines

Quoted 4 lines

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.

Quoted 2 lines

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

Quoted 40 lines · Tom Rini

Quoted 38 lines · Khem Raj

Quoted 28 lines · Tom Rini

Quoted 27 lines · Khem Raj

Quoted 25 lines · Tom Rini

Quoted 11 lines · Khem Raj

Quoted 10 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 8 lines

Quoted 5 lines

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.

Quoted 6 lines

Quoted 1 line

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

Quoted 4 lines

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

Quoted 41 lines · Khem Raj

Quoted 40 lines · Tom Rini

Quoted 38 lines · Khem Raj

Quoted 28 lines · Tom Rini

Quoted 27 lines · Khem Raj

Quoted 25 lines · Tom Rini

Quoted 11 lines · Khem Raj

Quoted 10 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 8 lines

Quoted 5 lines

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.

Quoted 6 lines

Quoted 1 line

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

Quoted 7 lines

Quoted 4 lines

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

Quoted 27 lines · Khem Raj

Quoted 25 lines · Tom Rini

Quoted 11 lines · Khem Raj

Quoted 10 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 8 lines

Quoted 5 lines

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.

Quoted 1 line

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.

Quoted 28 lines · Tom Rini

Quoted 27 lines · Khem Raj

Quoted 25 lines · Tom Rini

Quoted 11 lines · Khem Raj

Quoted 10 lines · Tom Rini

Quoted 8 lines · Khem Raj

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 8 lines

Quoted 5 lines

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.

Quoted 6 lines

Quoted 1 line

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.

Quoted 3 lines · 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.

there already are patches for 5.9 available too ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz

Quoted 6 lines · Khem Raj

Quoted 3 lines · 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.

Quoted 2 lines

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...

Quoted 6 lines · Khem Raj

Quoted 3 lines · 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.

Quoted 2 lines

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

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core