[OE-core] [PATCH 07/12] libunistring: upgrade to 0.9.10

[Randy MacLeod]

On 06/12/2018 07:18 AM, Maxin B. John wrote:
> License-Update: Checksum changed due to updation in documentation. There
> are no changes in the license terms.

That's correct but I'm not sure if we should include
a checksum on the (GPLv3) COPYING file since the README
says [1] that:
    This license is based on the GNU GPL version 3, see file COPYING.
I'd like to know if the COPYING file changed to say the _actual_
GPLv2 some day so a checksum would help track such changes.


The README statement is an odd way to convey the license terms.
Is this just standard FSFese?

The libunistring commit that sets out these terms is from 0.9:

commit 3c15d3a96963703fc02cddda7e968e508638d1b8
Author: Bruno Haible <bruno at clisp.org>
Date:   Sun Mar 15 02:10:58 2009 +0100

     License information.

  COPYING     | 674 ++++++++++++++++++++...++++++++++++++++++++
  COPYING.LIB | 165 +++++++++...++++++++
  ChangeLog   |   3 +
  README      |   2 +-
  4 files changed, 843 insertions(+), 1 deletion(-)


which doesn't help much other than the ChangeLog:

+       * COPYING.LIB: New file, from gnulib/doc/COPYING.LESSERv3.
+       * COPYING: New file, from gnulib/doc/COPYINGv3.


../Randy


[1] From README:

Copyright
---------

The libunistring library and its header files are dual-licensed under
"the GNU LGPLv3+ or the GNU GPLv2". This means, you can use it under either
   - the terms of the GNU Lesser General Public License (LGPL) version 3 or
     (at your option) any later version, or
   - the terms of the GNU General Public License (GPL) version 2, or
   - the same dual license "the GNU LGPLv3+ or the GNU GPLv2".

You find the GNU LGPL version 3 in the file COPYING.LIB.  This license is
based on the GNU GPL version 3, see file COPYING.

You can find the GNU GPL version 2 at
<https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>.

Note: This dual license makes it possible for the libunistring library
to be used by packages under GPLv2 or GPLv2+ licenses, in particular. See
the table in <https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility>.

The documentation is under another license; see in the documentation.

> 
> Signed-off-by: Maxin B. John <maxin.john at intel.com>
> ---
>   .../libunistring/{libunistring_0.9.9.bb => libunistring_0.9.10.bb}  | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>   rename meta/recipes-support/libunistring/{libunistring_0.9.9.bb => libunistring_0.9.10.bb} (85%)
> 
> diff --git a/meta/recipes-support/libunistring/libunistring_0.9.9.bb b/meta/recipes-support/libunistring/libunistring_0.9.10.bb
> similarity index 85%
> rename from meta/recipes-support/libunistring/libunistring_0.9.9.bb
> rename to meta/recipes-support/libunistring/libunistring_0.9.10.bb
> index ab7cba5..97fac4e 100644
> --- a/meta/recipes-support/libunistring/libunistring_0.9.9.bb
> +++ b/meta/recipes-support/libunistring/libunistring_0.9.10.bb
> @@ -16,15 +16,15 @@ SECTION = "devel"
>   LICENSE = "LGPLv3+ | GPLv2"
>   LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6 \
>                       file://README;beginline=45;endline=65;md5=08287d16ba8d839faed8d2dc14d7d6a5 \
> -                    file://doc/libunistring.texi;md5=efb80a3799a60f95feaf80661d4f204c \
> +                    file://doc/libunistring.texi;md5=287fa6075f78a3c85c1a52b0a92547cd \
>                      "
>   
>   SRC_URI = "${GNU_MIRROR}/libunistring/libunistring-${PV}.tar.gz \
>              file://iconv-m4-remove-the-test-to-convert-euc-jp.patch \
>              file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
>   "
> -SRC_URI[md5sum] = "4f689e37e4c3bd67de5786aa51d98b13"
> -SRC_URI[sha256sum] = "f5e90c08f9e5427ca3a2c0c53f19aa38b25c500913510ad25afef86448bea84a"
> +SRC_URI[md5sum] = "0d3274e9838396b12200f8b54ddaf43b"
> +SRC_URI[sha256sum] = "a82e5b333339a88ea4608e4635479a1cfb2e01aafb925e1290b65710d43f610b"
>   
>   inherit autotools texinfo
>   BBCLASSEXTEND = "native nativesdk"
> 


-- 
# Randy MacLeod
# Wind River Linux