# # spec file for package gpgme (Version 1.3.0) # # Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # # norootforbuild Name: gpgme BuildRequires: gpg2 >= 2.0.10 %if 0%{?suse_version} >= 1120 BuildRequires: libpth-devel >= 2.0.7 %else BuildRequires: pth >= 2.0.7 %endif BuildRequires: libgpg-error-devel >= 1.4 BuildRequires: libassuan-devel >= 1.1.0 License: GPLv2+ Group: Productivity/Security Requires: %install_info_prereq AutoReqProv: on Version: 1.3.0 Release: 3 Source: ftp://ftp.gnupg.org/gcrypt/gpgme/%{name}-%{version}.tar.bz2 Source2: baselibs.conf Url: http://www.gnupg.org/related_software/gpgme/ Summary: A Library Designed to Give Applications Easy Access to GnuPG Requires: gpg2 BuildRoot: %{_tmppath}/%{name}-%{version}-build %description GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a high-level Crypto API for encryption, decryption, signing, signature verification, and key management. Currently it uses GnuPG as its back-end, but the API is not restricted to this engine. Because the direct use of GnuPG from an application can be a complicated programming task, it is suggested that all software should try to use GPGME instead. This way bug fixes or improvements can be done at a central place and every application benefits from this. Authors of MUAs should especially consider using GPGME. Creating a set of standard widgets for common key selection tasks is even planned. Authors: -------- FSF - Code taken from GnuPG 1.0: gpgme/w32-util.c, GnuPG 1.1: jnlib/. g10 Code GmbH - All stuff since mid march 2001. Werner Koch - Design and most stuff. %package -n libgpgme11 License: GPLv2+ Summary: A Library Designed to give Applications easy Access to GnuPG Group: Development/Libraries/C and C++ Requires: gpgme = %{version} %description -n libgpgme11 GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a high-level Crypto API for encryption, decryption, signing, signature verification, and key management. Currently it uses GnuPG as its back-end, but the API is not restricted to this engine. Who Should use GPGME? Because the direct use of GnuPG from an application can be a complicated programming task, it is suggested that all software should try to use GPGME instead. This way bug fixes or improvements can be done at a central place and every application benefits from this. Authors of MUAs should especially consider using GPGME. Creating a set of standard widgets for common key selection tasks is even planned. Authors: -------- FSF - Code taken from GnuPG 1.0: gpgme/w32-util.c, GnuPG 1.1: jnlib/. g10 Code GmbH - All stuff since mid march 2001. Werner Koch - Design and most stuff. %package -n libgpgme-devel License: GPLv2+ Summary: A Library Designed to give Applications easy Access to GnuPG Group: Development/Libraries/C and C++ Requires: libgpgme11 = %{version} glibc-devel Requires: libgpg-error-devel %if 0%{?suse_version} >= 1120 Requires: libpth-devel %else Requires: pth %endif Requires: libassuan-devel Provides: gpgme-devel = %{version} Obsoletes: gpgme-devel < %{version} %description -n libgpgme-devel GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG easier for applications. It provides a high-level Crypto API for encryption, decryption, signing, signature verification, and key management. Currently it uses GnuPG as its back-end, but the API is not restricted to this engine. Who Should use GPGME? Because the direct use of GnuPG from an application can be a complicated programming task, it is suggested that all software should try to use GPGME instead. This way bug fixes or improvements can be done at a central place and every application benefits from this. Authors of MUAs should especially consider using GPGME. Creating a set of standard widgets for common key selection tasks is even planned. Authors: -------- FSF - Code taken from GnuPG 1.0: gpgme/w32-util.c, GnuPG 1.1: jnlib/. g10 Code GmbH - All stuff since mid march 2001. Werner Koch - Design and most stuff. %prep %setup -q %build sh autogen.sh # Ensure that a (re)build uses fixed binaries with minimum version because # in case configure picks GnuPG-1.x, e.g. from /usr/local, this would cause # testsuite failures: %configure --disable-static \ --with-gpg-version=2.0.10 \ --with-gpgsm-version=2.0.10 \ --with-gpgconf-version=2.0.10 \ --with-gpg=%_bindir/gpg2 \ --with-gpgsm=%_bindir/gpgsm \ --with-gpgconf=%_bindir/gpgconf %install %makeinstall # Do this now to make /usr/lib/rpm/brp-chuck-la happy: rm %buildroot/%_libdir/*.la %check make check %clean rm -rf $RPM_BUILD_ROOT %post -n libgpgme11 /sbin/ldconfig %postun -n libgpgme11 /sbin/ldconfig %post %install_info --info-dir=%{_infodir} %{_infodir}/gpgme.info.gz %postun %install_info_delete --info-dir=%{_infodir} %{_infodir}/gpgme.info.gz %files %defattr(-,root,root) %doc AUTHORS COPYING ChangeLog README NEWS THANKS TODO %{_datadir}/common-lisp %{_datadir}/common-lisp/source %{_infodir}/gpgme* %files -n libgpgme11 %defattr(-,root,root) %{_libdir}/libgpgme.so.* %{_libdir}/libgpgme-pthread.so.* %{_libdir}/libgpgme-pth.so.* %files -n libgpgme-devel %defattr(-,root,root) %{_libdir}/libgpgme.so %{_libdir}/libgpgme-pthread.so %{_libdir}/libgpgme-pth.so %{_bindir}/gpgme-config %{_datadir}/aclocal/gpgme.m4 %{_includedir}/gpgme.h %changelog