wok rev 24616

updated gpgme and gpgme-dev (1.13.1 -> 1.17.1)
author Hans-G?nter Theisgen
date Mon Mar 07 08:02:36 2022 +0100 (2022-03-07)
parents 26cb224c35b6
children 63c8af9d3a64
files gpgme-dev/receipt gpgme/description.txt gpgme/receipt
line diff
     1.1 --- a/gpgme-dev/receipt	Mon Mar 07 07:34:10 2022 +0100
     1.2 +++ b/gpgme-dev/receipt	Mon Mar 07 08:02:36 2022 +0100
     1.3 @@ -1,7 +1,7 @@
     1.4  # SliTaz package receipt.
     1.5  
     1.6  PACKAGE="gpgme-dev"
     1.7 -VERSION="1.13.1"
     1.8 +VERSION="1.17.1"
     1.9  CATEGORY="security"
    1.10  SHORT_DESC="C language library that allows to add support for cryptography to a program - development files."
    1.11  MAINTAINER="erjo@slitaz.org"
    1.12 @@ -15,6 +15,6 @@
    1.13  genpkg_rules()
    1.14  {
    1.15  	cp -a $install/*	$fs
    1.16 -	rm -r			$fs/usr/bin/gpgme-tool \
    1.17 -				$fs/usr/lib/*.so*
    1.18 +	rm -r			$fs/usr/bin/gpgme-tool
    1.19 +	rm -r			$fs/usr/lib/*.so*
    1.20  }
     2.1 --- a/gpgme/description.txt	Mon Mar 07 07:34:10 2022 +0100
     2.2 +++ b/gpgme/description.txt	Mon Mar 07 08:02:36 2022 +0100
     2.3 @@ -1,21 +1,3 @@
     2.4 -                  GPGME - GnuPG Made Easy
     2.5 -                ---------------------------
     2.6 -
     2.7 -         Copyright 2004, 2006, 2010, 2012, 2013, 2014, 2015 g10 Code GmbH
     2.8 -
     2.9 -This file is free software; as a special exception the author gives
    2.10 -unlimited permission to copy and/or distribute it, with or without
    2.11 -modifications, as long as this notice is preserved.
    2.12 -
    2.13 -This file is distributed in the hope that it will be useful, but
    2.14 -WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
    2.15 -implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
    2.16 -PURPOSE.
    2.17 -
    2.18 -
    2.19 -Introduction
    2.20 ---------------
    2.21 -
    2.22  GnuPG Made Easy (GPGME) is a C language library that allows to add
    2.23  support for cryptography to a program.  It is designed to make access
    2.24  to public key crypto engines like GnuPG or GpgSM easier for
    2.25 @@ -24,86 +6,3 @@
    2.26  
    2.27  GPGME uses GnuPG and GpgSM as its backends to support OpenPGP and the
    2.28  Cryptographic Message Syntax (CMS).
    2.29 -
    2.30 -GPGME runs best on GNU/Linux or *BSD systems.  Other Unices may
    2.31 -require small portability fixes, please send us your patches.
    2.32 -
    2.33 -See the files COPYING, COPYING.LESSER, and each file for copyright and
    2.34 -warranty information.  The file AUTHORS has a list of authors and
    2.35 -useful web and mail addresses.
    2.36 -
    2.37 -
    2.38 -Installation
    2.39 ---------------
    2.40 -
    2.41 -See the file INSTALL for generic installation instructions.
    2.42 -
    2.43 -Check that you have unmodified sources.  See below on how to do this.
    2.44 -Don't skip it - this is an important step!
    2.45 -
    2.46 -To build GPGME, you need to install libgpg-error (>= 1.11) and
    2.47 -Libassuan (>= 2.0.2).
    2.48 -
    2.49 -For support of the OpenPGP protocol (default), you should use the
    2.50 -latest version of GnuPG (>= 1.4) , available at:
    2.51 -ftp://ftp.gnupg.org/gcrypt/gnupg/.  For support of the CMS
    2.52 -(Cryptographic Message Syntax) protocol and lot of other features, you
    2.53 -need a GnuPG version >= 2.0.
    2.54 -
    2.55 -For building the GIT version of GPGME please see the file README.GIT
    2.56 -for more information.
    2.57 -
    2.58 -
    2.59 -How to Verify the Source
    2.60 ---------------------------
    2.61 -
    2.62 -In order to check that the version of GPGME which you are going to
    2.63 -install is an original and unmodified one, you can do it in one of the
    2.64 -following ways:
    2.65 -
    2.66 -a) If you have a trusted Version of GnuPG installed, you can simply check
    2.67 -   the supplied signature:
    2.68 -
    2.69 -	$ gpg --verify gpgme-x.y.z.tar.gz.sig
    2.70 -
    2.71 -   This checks that the detached signature gpgme-x.y.z.tar.gz.sig is
    2.72 -   indeed a a signature of gpgme-x.y.z.tar.gz.  The key used to create
    2.73 -   this signature is either of:
    2.74 -
    2.75 -   "pub  2048R/4F25E3B6 2011-01-12 Werner Koch (dist sig)"
    2.76 -   "pub  1024D/87978569 1999-05-13
    2.77 -                        Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
    2.78 -                        Marcus Brinkmann <mb@g10code.com>"
    2.79 -
    2.80 -   If you do not have this key, you can get it from any keyserver.  You
    2.81 -   have to make sure that this is really the key and not a faked one.
    2.82 -   You can do this by comparing the output of:
    2.83 -
    2.84 -	$ gpg --fingerprint 0x4F25E3B6
    2.85 -
    2.86 -   with the fingerprint published elsewhere.
    2.87 -
    2.88 -b) If you don't have any of the above programs, you have to verify
    2.89 -   the SHA1 checksum:
    2.90 -
    2.91 -	$ sha1sum gpgme-x.y.z.tar.gz
    2.92 -
    2.93 -   This should yield an output _similar_ to this:
    2.94 -
    2.95 -   fd9351b26b3189c1d577f0970f9dcadc3412def1  gpgme-x.y.z.tar.gz
    2.96 -
    2.97 -   Now check that this checksum is _exactly_ the same as the one
    2.98 -   published via the announcement list and probably via Usenet.
    2.99 -
   2.100 -
   2.101 -Documentation
   2.102 ----------------
   2.103 -
   2.104 -For information how to use the library you can read the info manual,
   2.105 -which is also a reference book, in the doc/ directory.  The programs
   2.106 -in the tests/gpg/ directory may also prove useful.
   2.107 -
   2.108 -Please subscribe to the gnupg-devel@gnupg.org mailing list if you want
   2.109 -to do serious work.
   2.110 -
   2.111 -For hacking on GPGME, please have a look at doc/HACKING.
     3.1 --- a/gpgme/receipt	Mon Mar 07 07:34:10 2022 +0100
     3.2 +++ b/gpgme/receipt	Mon Mar 07 08:02:36 2022 +0100
     3.3 @@ -1,7 +1,7 @@
     3.4  # SliTaz package receipt.
     3.5  
     3.6  PACKAGE="gpgme"
     3.7 -VERSION="1.13.1"
     3.8 +VERSION="1.17.1"
     3.9  CATEGORY="security"
    3.10  SHORT_DESC="C language library that allows to add support for cryptography to a program."
    3.11  MAINTAINER="erjo@slitaz.org"
    3.12 @@ -25,7 +25,7 @@
    3.13  compile_rules()
    3.14  {
    3.15  	# Integrity check: https://www.gnupg.org/download/integrity_check.html
    3.16 -	echo "f87f34e695e8d74ccc7c8f42864d50630afebb0e  $SRC/$TARBALL" | sha1sum -c || exit 1
    3.17 +	echo "73d5c863ba5478370b191e79b19733807fef529e  $SRC/$TARBALL" | sha1sum -c || exit 1
    3.18  
    3.19  	./configure		\
    3.20  		CC=gcc-83	\
    3.21 @@ -38,9 +38,6 @@
    3.22  # Rules to gen a SliTaz package suitable for Tazpkg.
    3.23  genpkg_rules()
    3.24  {
    3.25 -	mkdir -p $fs/usr/bin
    3.26 -	mkdir -p $fs/usr/lib
    3.27 -
    3.28 -	cp -a $install/usr/bin/gpgme-tool	$fs/usr/bin
    3.29 -	cp -a $install/usr/lib/*.so*		$fs/usr/lib
    3.30 +	cook_copy_files	gpgme-tool
    3.31 +	cook_copy_files	*.so*
    3.32  }