help2man update

help2man update

[Marko Lindqvist]

As part of systematic check for newer versions of GNU packages
I noticed this one, and it turned out to build as trivial
update (change version number, PR, checksums). But is help2man
actually used for anything? Many components that use it in
their upstream have patch to disable it in oe builds.


 - ML

[PATCH] help2man: update to upstream version 1.40.13

[Marko Lindqvist]

Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
---
 .../{help2man-native_1.38.2.bb => help2man-native_1.40.13.bb}    |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-devtools/help2man/{help2man-native_1.38.2.bb => help2man-native_1.40.13.bb} (78%)

diff --git a/meta/recipes-devtools/help2man/help2man-native_1.38.2.bb b/meta/recipes-devtools/help2man/help2man-native_1.40.13.bb
similarity index 78%
rename from meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
rename to meta/recipes-devtools/help2man/help2man-native_1.40.13.bb
index bea7fe9..9413f52 100644
--- a/meta/recipes-devtools/help2man/help2man-native_1.38.2.bb
+++ b/meta/recipes-devtools/help2man/help2man-native_1.40.13.bb
@@ -3,11 +3,11 @@ SECTION = "devel"
 LICENSE = "GPLv3"
 LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
 DEPENDS = "autoconf-native automake-native"
-PR = "r2"
+PR = "r0"
 
 SRC_URI = "${GNU_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz"
-SRC_URI[md5sum] = "426671c6fe79e5ef2233303367eab5a6"
-SRC_URI[sha256sum] = "952c29561bce8b233aa10af7f0e0c79c8243712810bf8ddf01e6efd82ce250d1"
+SRC_URI[md5sum] = "ecbc98f1f146e404e85d7bef520b34d8"
+SRC_URI[sha256sum] = "15d3b6ebbac90f6d2a21480ba5e33c03b480a342ce498a84b1804f03d75358ba"
 
 inherit autotools native
 
-- 
1.7.10.4

Re: help2man update

[Mark Hatle]

On 12/14/12 1:19 PM, Marko Lindqvist wrote:
>
> As part of systematic check for newer versions of GNU packages
> I noticed this one, and it turned out to build as trivial
> update (change version number, PR, checksums). But is help2man
> actually used for anything? Many components that use it in
> their upstream have patch to disable it in oe builds.

It is unfortunately needed to build a number of things.  In addition, we do want 
to have working man pages available for some configurations.  So this uprev 
looks like a very good idea to me.

--Mark

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