4
4
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
5
Uploaders: Jan Niehusmann <jan@debian.org>
6
Build-Depends: debhelper (>= 4.0.0), libqt4-dev (>= 4.1.0-3), docbook-to-man
5
Uploaders: Jan Niehusmann <jan@debian.org>, Matthew Rosewarne <mrosewarne@inoutbox.com>
6
Build-Depends: cdbs (>= 0.4.51), debhelper (>= 6), quilt, libqt4-dev, ca-certificates
7
7
Build-Conflicts: qca-dev, libqca2-dev
8
Standards-Version: 3.7.2
8
Standards-Version: 3.7.3
9
Homepage: http://delta.affinix.com/qca/
14
Depends: ${shlibs:Depends}, ${misc:Depends}
15
Suggests: libqca2-plugin-cyrus-sasl, libqca2-plugin-gnupg, libqca2-plugin-ossl, libqca2-plugin-pkcs11
16
Conflicts: libqca2-plugin-gnupg (<< 0.1~20070904-1), libqca2-plugin-ossl (<< 0.1~20070904-1)
17
Description: libraries for the Qt Cryptographic Architecture
18
The Qt Cryptographic Architecture provides a straightforward and cross-
19
platform API for a range of cryptographic features, including SSL/TLS,
20
X.509 certificates, SASL, OpenPGP, S/MIME CMS, and smart cards.
10
22
Package: libqca2-dev
13
25
Depends: libqca2 (= ${binary:Version}), libqt4-dev
26
Suggests: libqca2-doc (= ${source:Version})
15
Description: Qt Cryptographic Architecture - development files
16
Taking a hint from the similarly-named Java Cryptography Architecture,
17
QCA aims to provide a straightforward and cross-platform crypto API,
18
using Qt datatypes and conventions. QCA separates the API from the
19
implementation, using plugins known as Providers. The advantage of
20
this model is to allow applications to avoid linking to or explicitly
21
depending on any particular cryptographic library. This allows one to
22
easily change or upgrade crypto implementations without even needing
23
to recompile the application!
28
Description: development files for the Qt Cryptographic Architecture
29
The Qt Cryptographic Architecture provides a straightforward and cross-
30
platform API for a range of cryptographic features, including SSL/TLS,
31
X.509 certificates, SASL, OpenPGP, S/MIME CMS, and smart cards.
25
This package contains the files necessary to compile applications
33
This package contains development files for building software that uses the
34
Qt Cryptographic Architecture.
31
39
Depends: ${shlibs:Depends}, ${misc:Depends}
32
Conflicts: libqca2-plugin-gnupg (<< 0.1~20070904-1), libqca2-plugin-ossl (<< 0.1~20070904-1)
33
Description: Qt Cryptographic Architecture - shared library
34
Taking a hint from the similarly-named Java Cryptography Architecture,
35
QCA aims to provide a straightforward and cross-platform crypto API,
36
using Qt datatypes and conventions. QCA separates the API from the
37
implementation, using plugins known as Providers. The advantage of
38
this model is to allow applications to avoid linking to or explicitly
39
depending on any particular cryptographic library. This allows one to
40
easily change or upgrade crypto implementations without even needing
41
to recompile the application!
41
Suggests: libqca2-dev (= ${source:Version})
42
Description: API documentation for the Qt Cryptographic Architecture
43
The Qt Cryptographic Architecture provides a straightforward and cross-
44
platform API for a range of cryptographic features, including SSL/TLS,
45
X.509 certificates, SASL, OpenPGP, S/MIME CMS, and smart cards.
43
This package contains the files necessary to run applications
47
This package contains documentation for developers working with the
48
Qt Cryptographic Architecture.
added
removed
debian/control
