/tags/1.0.19-1/debian/docs |
---|
0,0 → 1,0 |
debian/yahoo-patent-license-1.2.txt |
/tags/1.0.19-1/debian/changelog |
---|
0,0 → 1,39 |
libdkim (1:1.0.19-1) unstable; urgency=low |
* New upstream release. |
- Drop remaining patches; issues fixed upstream. |
* New maintainer email address. |
* Include Yahoo! patent license as plain text. |
-- Magnus Holmgren <holmgren@debian.org> Sat, 17 May 2008 23:13:03 +0200 |
libdkim (1:1.0.17-1) unstable; urgency=low |
* New upstream release. |
* Drop 20_winmacros.dpatch; fixed upstream. |
* Bump soname to libdkim1 because of incompatible struct changes. |
* 20_strict_includes.dpatch (new): Add "#include <string.h>" as necessary |
to fix FTBFS with GCC 4.3 (Closes: #455145). |
* Add an epoch to reclaim binary packages "stolen" by dkim-milter. |
* Dump the linker version script - changing the soname when necessary is |
going to be hard enough. |
* Move homepage URL from description to control field. |
* Increase Standards-Version to 3.7.3 without changes. |
* Don't ignore distclean errors. |
-- Magnus Holmgren <magnus@kibibyte.se> Fri, 15 Feb 2008 23:04:42 +0100 |
libdkim (1.0.14-1) unstable; urgency=low |
* New upstream release. |
* Build-depend on pkg-config. |
* Use dpatch to apply changes to upstream. |
-- Magnus Holmgren <magnus@kibibyte.se> Wed, 02 May 2007 21:14:01 +0200 |
libdkim (1.0.13-1) unstable; urgency=low |
* Initial release (Closes: #410829). |
-- Magnus Holmgren <magnus@kibibyte.se> Tue, 6 Mar 2007 21:08:04 +0100 |
/tags/1.0.19-1/debian/yahoo-patent-license-1.2.txt |
---|
0,0 → 1,167 |
Yahoo! DomainKeys Patent License Agreement v1.2 |
Copyright (c) 2006, Yahoo! Inc. |
All rights reserved. |
This Yahoo! DomainKeys Patent License Agreement (this "Agreement") is |
between Yahoo! Inc. ("Yahoo!") and you ("Licensee"). By attempting to |
exercise any rights granted under this Agreement, Licensee agrees to be |
bound by all the terms and conditions set forth below, and subject to those |
terms and conditions, Licensee may use the intellectual property described |
below. |
1. LICENSE GRANT. |
1.1. Subject to the terms and conditions of this Agreement, Licensor hereby |
grants You a royalty-free, perpetual, worldwide, sublicensable, |
non-exclusive license under its rights to the Yahoo! Patent Claims to make, |
use, sell, offer for sale, and/or import Implementations. |
2. DEFINITIONS. |
2.1. "DomainKeys Developer(s)" means Yahoo, Inc. ("Yahoo!"), Licensor, |
and/or any other individual or entity who distributes Implementations under |
this Agreement. |
2.2. "Implementations" means the specific portions of a hardware or |
software implementation expressly required to be compliant with the |
Specifications for the sole purpose of a sender verification solution in |
connection with e-mail. |
2.3. "Licensor" means Yahoo! or any other individual or entity that elects |
to use this Agreement to license Yahoo! Patent Claims to any licensee. |
2.4. "Specifications" means the specification having submission ID |
"draft-delany-domainkeys-base-01.txt" dated Aug 2004 published through the |
IETF (Internet Engineering Task Force). The Specifications may be found at |
the following link: |
http://antispam.yahoo.com/domainkeys/draft-delany-domainkeys-base-01.txt |
2.5. "Yahoo! Patent Claims" shall mean those claims of all Yahoo! foreign |
and domestic patents and patent applications that base their priority on |
U.S. Provisional Patent Application Ser. Nos. 60/497,794, filed Aug. 26, |
2003, or 60/553,300, filed Mar. 15, 2004, or U.S. Patent Application Ser. |
Nos. 10/671,319, filed Sep. 24, 2003, or 10/805,181, filed Mar. 19, 2004. |
2.6. "You" or "Your" means an individual, company, or other legal entity |
exercising any rights under this Agreement. Any individual who accepts the |
terms and conditions of this Agreement on behalf of a company or other |
legal entity represents and warrants that the individual has the authority |
to enter into this Agreement on behalf of the company or other legal |
entity. |
3. TERMS. |
3.1. You agree not to assert against Yahoo!, any other DomainKeys Developer |
or any of their respective licensees under Section 3.4, a patent |
infringement claim based on the manufacture, use, sale, offer for sale |
and/or importation of any Implementations ("Implementation IP Claim"). |
3.2. To indicate your assent to the terms and conditions of this Agreement |
and in order to obtain a license to make, use, sell, offer for sale, and/or |
import Implementations, You must include, attach or preserve the following |
prominently displayed statement in the source code and object code of any |
such Implementations: "This code incorporates intellectual property owned |
by Yahoo! and licensed pursuant to the Yahoo! DomainKeys Patent License |
Agreement.". |
3.3. You will not use the name of Yahoo! to endorse or promote any |
products, services, or Implementations without specific prior written |
permission of Yahoo!. "DomainKeys" is a trademark of Yahoo!. However, You |
may state Your Implementations are "DomainKeys compliant", "supports |
DomainKeys", or is "DomainKeys-enabled", without citation to Yahoo!. You |
must create Your own product or service names or trademarks for Your |
Implementations and You agree not to use the term "DomainKeys" in or as |
part of a name or trademark for Your Implementations. |
3.4. You may choose to distribute Implementations under this Agreement or a |
different agreement, provided that: |
(a) a copy of this Agreement or the different agreement is included with |
each Implementation along with the following prominently displayed |
statement: "By making, using, selling, offering for sale, importing, |
and/or sublicensing Implementations as permitted, you agree to the terms |
and conditions of the Yahoo! DomainKeys Patent License Agreement or |
other agreement contained herein."; and |
(b) if distributed under a different agreement, such different agreement |
contains terms and conditions that (i) provide no fewer rights, |
privileges and immunities to DomainKeys Developers than the terms and |
conditions of this Agreement, including, without limitation, Sections |
1.1, 3.1, 3.4, 3.7, 4.1, 4.2, and 4.3. |
3.5. You acknowledge that implementations of the Specifications may be |
subject to U.S. export restriction and other applicable national and |
international laws. You agree to comply with all export, re-export, or |
import restrictions, laws, or regulations. |
3.6. Yahoo!, and only Yahoo!, may, from time to time and at its sole |
discretion, update or modify the terms of this Agreement. If Yahoo! makes |
any such modifications, You may continue under the terms and conditions of |
this Agreement or agree to the updated or modified terms and conditions. |
For the most recent version of this Agreement please contact Yahoo!. |
3.7. This Agreement and the rights hereunder will terminate: |
(a) automatically without notice from Yahoo!, if You at any time during |
the term of this Agreement assert any Implementation IP Claim against |
Yahoo!; |
(b) upon written notice from Yahoo!, if You at any time during the term |
of this Agreement assert any Implementation IP Claim against any |
DomainKeys Developer (other than Yahoo!) or any licensees of any |
DomainKeys Developer; or |
(c) where (a) or (b) do not apply, automatically without notice from |
Yahoo!, if You fail to comply with any term(s) of this Agreement and |
fail to cure such breach within 30 days of You becoming aware of such |
breach. |
3.8. This Agreement constitutes the entire agreement between the parties |
with respect to the subject matter hereof. This Agreement shall be governed |
by and construed under the laws of the United States and the State of |
California without giving effect to California conflict of law provisions |
or to construction provisions favoring either party. All actions arising |
out of or relating to this Agreement that involve Yahoo! as a party will be |
adjudicated exclusively by the Superior Court of the State of California |
for the County of Santa Clara or the United States District Court for the |
Northern District of California. |
3.9. In the event that any provision of this Agreement is deemed to be |
invalid, such invalidity shall not affect the remainder of this Agreement. |
4. LEGAL DISCLAIMERS. |
4.1. THE YAHOO! PATENT CLAIMS, THIS AGREEMENT, THE DOMAINKEYS TRADEMARK, |
AND THE SPECIFICATIONS ARE PROVIDED ON AN "AS IS" BASIS, WITHOUT |
REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR |
IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATIONS, WARRANTIES OR |
CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A |
PARTICULAR PURPOSE. You are solely responsible for determining the |
appropriateness of exercising any rights under this Agreement and using the |
Specifications and the DomainKeys trademark and assume all risks associated |
in connection therewith, including, but not limited to, the risks and costs |
of program errors, compliance with applicable laws, damage to or loss of |
data, programs or equipment, and unavailability or interruption of |
operations. |
4.2. You expressly acknowledge and agree that no assurances are provided by |
DomainKeys Developers with respect to the validity of the Yahoo! Patent |
Claims or that the Specifications, the DomainKeys trademark or any |
implementations related to the Specifications or the DomainKeys trademark |
do not infringe or misappropriate the patent, trademark or other |
intellectual property rights of any other entity. DomainKeys Developers |
disclaim any liability to You for claims brought by any other person or |
entity based on infringement or misappropriation of intellectual property |
rights or otherwise. As a condition to exercising the rights and licenses |
granted hereunder, You hereby assume sole responsibility to secure any |
other intellectual property rights needed. |
4.3. DOMAINKEYS DEVELOPERS SHALL NOT HAVE ANY LIABILITY FOR ANY DIRECT, |
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES |
(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY |
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE EXERCISE |
OF ANY RIGHTS UNDER THIS AGREEMENT, EVEN IF ADVISED OF THE POSSIBILITY OF |
SUCH DAMAGES, AND EVEN IF THE REMEDIES PROVIDED FOR IN THIS AGREEMENT FAIL |
OF THEIR ESSENTIAL PURPOSE. |
/tags/1.0.19-1/debian/control |
---|
0,0 → 1,42 |
Source: libdkim |
Priority: optional |
Maintainer: Magnus Holmgren <holmgren@debian.org> |
Build-Depends: debhelper (>= 5), autoconf, libssl-dev, pkg-config, dpatch |
Standards-Version: 3.7.3 |
Section: libs |
Homepage: http://libdkim.sourceforge.net |
Package: libdkim1 |
Section: libs |
Architecture: any |
Depends: ${shlibs:Depends}, ${misc:Depends} |
Description: cryptographically identify the sender of email |
DomainKeys Identified Mail (DKIM) defines a domain-level |
authentication framework for email using public-key cryptography and |
key server technology to permit verification of the source and |
contents of messages by either Mail Transport Agents (MTAs) or Mail |
User Agents (MUAs). |
. |
libdkim is a library, developed by Alt-N Technologies, that allows |
incorporating DKIM into an existing MTA or other application. It |
provides full support for signing, verifying, and SSP. See the |
changelogs for information on compliance with specifications. |
Package: libdkim-dev |
Section: libdevel |
Architecture: any |
Depends: libdkim1 (= ${binary:Version}), libssl-dev |
Description: cryptographically identify the sender of email |
DomainKeys Identified Mail (DKIM) defines a domain-level |
authentication framework for email using public-key cryptography and |
key server technology to permit verification of the source and |
contents of messages by either Mail Transport Agents (MTAs) or Mail |
User Agents (MUAs). |
. |
libdkim is a library, developed by Alt-N Technologies, that allows |
incorporating DKIM into an existing MTA or other application. It |
provides full support for signing, verifying, and SSP. See the |
changelogs for information on compliance with specifications. |
. |
This package contains the development files needed to compile and link |
programs with libdkim. |
/tags/1.0.19-1/debian/patches/00list |
---|
--- tags/1.0.19-1/debian/patches/20_strict_includes.dpatch (nonexistent) |
+++ tags/1.0.19-1/debian/patches/20_strict_includes.dpatch (revision 27) |
@@ -0,0 +1,29 @@ |
+#! /bin/sh /usr/share/dpatch/dpatch-run |
+## 20_strict_includes.dpatch by Magnus Holmgren <magnus@kibibyte.se> |
+## |
+## All lines beginning with `## DP:' are a description of the patch. |
+## DP: Add "#include <string.h>" as needed to fix FTBFS with GCC 4.3. |
+ |
+@DPATCH@ |
+diff -urNad trunk~/src/dkim.cpp trunk/src/dkim.cpp |
+--- trunk~/src/dkim.cpp 2007-09-04 14:38:44.000000000 +0200 |
++++ trunk/src/dkim.cpp 2008-01-19 23:32:38.000000000 +0100 |
+@@ -20,6 +20,7 @@ |
+ #else |
+ #endif |
+ |
++#include <string.h> |
+ #include "dkim.h" |
+ #include "dkimsign.h" |
+ #include "dkimverify.h" |
+diff -urNad trunk~/src/dkimverify.cpp trunk/src/dkimverify.cpp |
+--- trunk~/src/dkimverify.cpp 2007-10-29 15:15:18.000000000 +0100 |
++++ trunk/src/dkimverify.cpp 2008-01-19 23:32:50.000000000 +0100 |
+@@ -29,6 +29,7 @@ |
+ #include <assert.h> |
+ #include <vector> |
+ #include <algorithm> |
++#include <string.h> |
+ |
+ #define MAX_SIGNATURES 10 // maximum number of DKIM signatures to process in a message |
+ |
/tags/1.0.19-1/debian/patches/20_strict_includes.dpatch |
---|
Property changes: |
Added: svn:executable |
## -0,0 +1 ## |
+* |
\ No newline at end of property |
Index: tags/1.0.19-1/debian/patches/20_bad_test.dpatch |
=================================================================== |
--- tags/1.0.19-1/debian/patches/20_bad_test.dpatch (nonexistent) |
+++ tags/1.0.19-1/debian/patches/20_bad_test.dpatch (revision 27) |
@@ -0,0 +1,20 @@ |
+#! /bin/sh /usr/share/dpatch/dpatch-run |
+## 20_bad_test.dpatch by Magnus Holmgren <magnus@kibibyte.se> |
+## |
+## All lines beginning with `## DP:' are a description of the patch. |
+## DP: Change pfnPolicyCallback to pfnPracticesCallback in test |
+## DP: program. |
+ |
+@DPATCH@ |
+diff -urNad trunk~/src/libdkimtest.cpp trunk/src/libdkimtest.cpp |
+--- trunk~/src/libdkimtest.cpp 2007-02-22 17:05:46.000000000 +0100 |
++++ trunk/src/libdkimtest.cpp 2008-01-19 22:47:48.000000000 +0100 |
+@@ -256,7 +256,7 @@ |
+ |
+ DKIMVerifyOptions vopts; |
+ vopts.pfnSelectorCallback = NULL; //SelectorCallback; |
+- vopts.pfnPolicyCallback = NULL; //PolicyCallback; |
++ vopts.pfnPracticesCallback = NULL; //PolicyCallback; |
+ |
+ n = DKIMVerifyInit( &ctxt, &vopts ); |
+ |
/tags/1.0.19-1/debian/patches/20_bad_test.dpatch |
---|
Property changes: |
Added: svn:executable |
## -0,0 +1 ## |
+* |
\ No newline at end of property |
Index: tags/1.0.19-1/debian/configure.ac |
=================================================================== |
--- tags/1.0.19-1/debian/configure.ac (nonexistent) |
+++ tags/1.0.19-1/debian/configure.ac (revision 27) |
@@ -0,0 +1,38 @@ |
+# -*- Autoconf -*- |
+# Process this file with autoconf to produce a configure script. |
+ |
+AC_PREREQ(2.61) |
+AC_INIT(libdkim, 1.0.19) |
+AC_CONFIG_SRCDIR([dkim.cpp]) |
+##AC_CONFIG_HEADER([config.h]) |
+ |
+# Checks for programs. |
+AC_PROG_CXX |
+PKG_PROG_PKG_CONFIG |
+ |
+# Checks for libraries. |
+#AC_CHECK_LIB([crypto], [PEM_read_PrivateKey]) |
+PKG_CHECK_MODULES([libcrypto], [libcrypto]) |
+AC_SEARCH_LIBS([res_query], [resolv c],, |
+ [AC_SEARCH_LIBS(__res_query,resolv bind)]) |
+ |
+# Checks for header files. |
+AC_HEADER_RESOLV |
+AC_HEADER_STDC |
+AC_CHECK_HEADERS([netdb.h netinet/in.h inttypes.h stdlib.h string.h]) |
+ |
+# Checks for typedefs, structures, and compiler characteristics. |
+AC_HEADER_STDBOOL |
+AC_C_CONST |
+AC_C_INLINE |
+AC_HEADER_TIME |
+AC_TYPE_UINT16_T |
+AC_TYPE_UINT32_T |
+ |
+# Checks for library functions. |
+AC_FUNC_MEMCMP |
+AC_FUNC_SELECT_ARGTYPES |
+AC_CHECK_FUNCS([select socket strchr]) |
+ |
+AC_CONFIG_FILES([Makefile libdkim.pc]) |
+AC_OUTPUT |
Index: tags/1.0.19-1/debian/rules |
=================================================================== |
--- tags/1.0.19-1/debian/rules (nonexistent) |
+++ tags/1.0.19-1/debian/rules (revision 27) |
@@ -0,0 +1,85 @@ |
+#!/usr/bin/make -f |
+# -*- makefile -*- |
+# Sample debian/rules that uses debhelper. |
+# This file was originally written by Joey Hess and Craig Small. |
+# As a special exception, when this file is copied by dh-make into a |
+# dh-make output file, you may use that output file without restriction. |
+# This special exception was added by Craig Small in version 0.37 of dh-make. |
+ |
+# Uncomment this to turn on verbose mode. |
+#export DH_VERBOSE=1 |
+ |
+include /usr/share/dpatch/dpatch.make |
+ |
+export CXXFLAGS = -Wall -g |
+ |
+ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) |
+ CXXFLAGS += -O0 |
+else |
+ CXXFLAGS += -O2 |
+endif |
+ |
+configure: config.status |
+config.status: $(DPATCH_STAMPFN) debian/configure.ac |
+ dh_testdir |
+ ln -sf $(CURDIR)/debian/*.in src/ |
+ cd debian && autoconf |
+ debian/configure --srcdir=src/ --prefix=/usr |
+ |
+build: build-stamp |
+build-stamp: config.status |
+ dh_testdir |
+ |
+ $(MAKE) |
+ |
+ touch $@ |
+ |
+clean: clean-patched unpatch |
+clean-patched: |
+ dh_testdir |
+ dh_testroot |
+ rm -f build-stamp configure-stamp |
+ |
+ [ ! -f Makefile ] || $(MAKE) distclean |
+ |
+ rm -f src/*.in debian/configure |
+ rm -rf debian/autom4te.cache |
+ dh_clean |
+ |
+install: build |
+ dh_testdir |
+ dh_testroot |
+ dh_clean -k |
+ dh_installdirs |
+ |
+ $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp |
+# |
+ |
+ |
+# Build architecture-independent files here. |
+binary-indep: build install |
+# We have nothing to do by default. |
+ |
+# Build architecture-dependent files here. |
+binary-arch: build install |
+ dh_testdir |
+ dh_testroot |
+ dh_install --sourcedir=debian/tmp |
+ dh_link |
+ dh_installchangelogs -k README |
+ dh_installdocs |
+ dh_installexamples |
+# dh_installinfo |
+# dh_installman |
+ dh_strip |
+ dh_compress |
+ dh_fixperms |
+ dh_makeshlibs |
+ dh_installdeb |
+ dh_shlibdeps |
+ dh_gencontrol |
+ dh_md5sums |
+ dh_builddeb |
+ |
+binary: binary-indep binary-arch |
+.PHONY: patch unpatch build clean binary-indep binary-arch binary install configure |
/tags/1.0.19-1/debian/rules |
---|
Property changes: |
Added: svn:executable |
## -0,0 +1 ## |
+* |
\ No newline at end of property |
Index: tags/1.0.19-1/debian/Makefile.in |
=================================================================== |
--- tags/1.0.19-1/debian/Makefile.in (nonexistent) |
+++ tags/1.0.19-1/debian/Makefile.in (revision 27) |
@@ -0,0 +1,91 @@ |
+# libdkim makefile for UNIX |
+# |
+srcdir = @srcdir@ |
+VPATH = @srcdir@ |
+ |
+prefix = @prefix@ |
+exec_prefix = @exec_prefix@ |
+bindir = @bindir@ |
+libdir = @libdir@ |
+includedir = @includedir@ |
+ |
+OBJEXT = @OBJEXT@ |
+LIBS = @LIBS@ @libcrypto_LIBS@ |
+ |
+CC = @CC@ |
+CXX = @CXX@ |
+ |
+CFLAGS = @CFLAGS@ |
+CXXFLAGS = @CXXFLAGS@ |
+CPPFLAGS = @CPPFLAGS@ |
+ |
+INCL = |
+LDFLAGS = @LDFLAGS@ |
+ |
+libdkim_SOURCES = dkim.cpp dns.cpp dkimbase.cpp dkimsign.cpp dkimverify.cpp |
+HEADERS = dkim.h dns.h dkimbase.h dkimsign.h dkimverify.h |
+ |
+libdkim_OBJS = $(libdkim_SOURCES:.cpp=.$(OBJEXT)) |
+libdkim_PURE_OBJS = $(libdkim_SOURCES:.cpp=.p$(OBJEXT)) |
+ |
+libdkimtest_SOURCES = libdkimtest.cpp |
+libdkimtest_OBJS = libdkimtest.$(OBJEXT) |
+ |
+SHLIBFORLINK = libdkim.so |
+SHLIBSONAME = $(SHLIBFORLINK).$(SHLIBMAJOR) |
+SHLIBTARGET = $(SHLIBFORLINK) |
+SHLIBLINK = $(CXX) $(LDFLAGS) -shared -Wl,-soname=$(SHLIBSONAME) |
+SHLIBMAJOR = 1 |
+SHLIBMINOR = 0 |
+SHLIBFILE = $(SHLIBSONAME).$(SHLIBMINOR) |
+SHLIBCFLAGS = -fPIC |
+ |
+ARFLAGS = crs |
+ |
+TARGETS = libdkim.a $(SHLIBTARGET) libdkimtest |
+ |
+all: $(TARGETS) |
+ |
+libdkim.a: $(libdkim_OBJS) |
+ -rm -f $@ |
+ $(AR) $(ARFLAGS) $@ $(libdkim_OBJS) |
+ |
+$(SHLIBFORLINK): $(libdkim_PURE_OBJS) |
+ $(SHLIBLINK) -o $@ $(LIBS) $(libdkim_PURE_OBJS) |
+ -mkdir .lib 2>/dev/null |
+ [ -z "$(SHLIBSONAME)" ] || (cd .lib \ |
+ && ln -sf ../$(SHLIBFORLINK) $(SHLIBSONAME)) |
+ |
+libdkimtest: $(libdkimtest_OBJS) libdkim.a |
+ $(CXX) -static -o $@ libdkimtest.o libdkim.a $(LIBS) |
+ |
+libdkimtest.o: $(libdkimtest_SOURCES) $(HDRS) |
+ $(CXX) $(CXXFLAGS) -o $@ -c $< |
+ |
+%.$(OBJEXT): %.cpp $(HDRS) |
+ $(CXX) $(CXXFLAGS) -o $@ -c $< |
+ |
+%.p$(OBJEXT): %.cpp $(HDRS) |
+ $(CXX) $(SHLIBCFLAGS) $(CXXFLAGS) -o $@ -c $< |
+ |
+clean: |
+ -rm -f *.$(OBJEXT) *.p$(OBJEXT) $(TARGETS) |
+ -rm -rf .lib |
+ |
+distclean: clean |
+ -rm -f config.status config.log Makefile libdkim.pc |
+ |
+install: all |
+ install -m 755 -d $(DESTDIR)$(libdir) |
+ install -m 755 -d $(DESTDIR)$(libdir)/pkgconfig |
+ install -m 755 -d $(DESTDIR)$(includedir) |
+ install -m 644 libdkim.a $(DESTDIR)$(libdir) |
+ install -m 755 $(SHLIBFORLINK) $(DESTDIR)$(libdir)/$(SHLIBFILE) |
+ [ -z "$(SHLIBSONAME)" ] \ |
+ || (cd $(DESTDIR)$(libdir) \ |
+ && ln -sf $(SHLIBFILE) $(SHLIBSONAME) \ |
+ && ln -sf $(SHLIBFILE) $(SHLIBFORLINK) ) |
+ install -m 644 $(srcdir)/dkim.h $(DESTDIR)$(includedir) |
+ install -m 644 libdkim.pc $(DESTDIR)$(libdir)/pkgconfig |
+ |
+.PHONY: all install clean distclean |
Index: tags/1.0.19-1/debian/libdkim-dev.links |
=================================================================== |
--- tags/1.0.19-1/debian/libdkim-dev.links (nonexistent) |
+++ tags/1.0.19-1/debian/libdkim-dev.links (revision 27) |
@@ -0,0 +1 @@ |
+usr/share/doc/libdkim1 usr/share/doc/libdkim-dev |
Index: tags/1.0.19-1/debian/install |
=================================================================== |
--- tags/1.0.19-1/debian/install (nonexistent) |
+++ tags/1.0.19-1/debian/install (revision 27) |
@@ -0,0 +1 @@ |
+usr/lib/lib*.so.* |
Index: tags/1.0.19-1/debian/libdkim.pc.in |
=================================================================== |
--- tags/1.0.19-1/debian/libdkim.pc.in (nonexistent) |
+++ tags/1.0.19-1/debian/libdkim.pc.in (revision 27) |
@@ -0,0 +1,12 @@ |
+prefix=@prefix@ |
+exec_prefix=@exec_prefix@ |
+libdir=@libdir@ |
+includedir=@includedir@ |
+ |
+Name: @PACKAGE_NAME@ |
+Description: DomainKeys Identified Mail library from Alt-N Inc. |
+Version: @PACKAGE_VERSION@ |
+Requires.private: libcrypto |
+Libs: -L${libdir} -ldkim |
+Libs.private: @LIBS@ |
+Cflags: -I${includedir} |
Index: tags/1.0.19-1/debian/compat |
=================================================================== |
--- tags/1.0.19-1/debian/compat (nonexistent) |
+++ tags/1.0.19-1/debian/compat (revision 27) |
@@ -0,0 +1 @@ |
+5 |
Index: tags/1.0.19-1/debian/libdkim-dev.install |
=================================================================== |
--- tags/1.0.19-1/debian/libdkim-dev.install (nonexistent) |
+++ tags/1.0.19-1/debian/libdkim-dev.install (revision 27) |
@@ -0,0 +1,4 @@ |
+usr/include/* |
+usr/lib/lib*.a |
+usr/lib/lib*.so |
+usr/lib/pkgconfig |
Index: tags/1.0.19-1/debian/libdkim.ver |
=================================================================== |
--- tags/1.0.19-1/debian/libdkim.ver (nonexistent) |
+++ tags/1.0.19-1/debian/libdkim.ver (revision 27) |
@@ -0,0 +1,4 @@ |
+DKIM_0.0 { |
+ global: DKIM*; |
+ local: *; |
+}; |
Index: tags/1.0.19-1/debian/watch |
=================================================================== |
--- tags/1.0.19-1/debian/watch (nonexistent) |
+++ tags/1.0.19-1/debian/watch (revision 27) |
@@ -0,0 +1,4 @@ |
+# Compulsory line, this is a version 3 file |
+version=3 |
+ |
+http://sf.net/libdkim/libdkim-(.*)\.zip debian uupdate |
Index: tags/1.0.19-1/debian/copyright |
=================================================================== |
--- tags/1.0.19-1/debian/copyright (nonexistent) |
+++ tags/1.0.19-1/debian/copyright (revision 27) |
@@ -0,0 +1,217 @@ |
+This package was debianized by Magnus Holmgren <magnus@kibibyte.se> on |
+19 Feb 2007. |
+ |
+It was downloaded from http://libdkim.sf.net (the easiest way to get the |
+original zip file is via http://qa.debian.org/watch/sf.php/libdkim/). |
+ |
+Upstream Author: Alt-N Technologies, http://www.altn.com |
+ |
+Copyright 2005 Alt-N Technologies, Ltd. |
+ |
+License: |
+ |
+ Apache License |
+ Version 2.0, January 2004 |
+ http://www.apache.org/licenses/ |
+ |
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION |
+ |
+ 1. Definitions. |
+ |
+ "License" shall mean the terms and conditions for use, reproduction, |
+ and distribution as defined by Sections 1 through 9 of this document. |
+ |
+ "Licensor" shall mean the copyright owner or entity authorized by |
+ the copyright owner that is granting the License. |
+ |
+ "Legal Entity" shall mean the union of the acting entity and all |
+ other entities that control, are controlled by, or are under common |
+ control with that entity. For the purposes of this definition, |
+ "control" means (i) the power, direct or indirect, to cause the |
+ direction or management of such entity, whether by contract or |
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the |
+ outstanding shares, or (iii) beneficial ownership of such entity. |
+ |
+ "You" (or "Your") shall mean an individual or Legal Entity |
+ exercising permissions granted by this License. |
+ |
+ "Source" form shall mean the preferred form for making modifications, |
+ including but not limited to software source code, documentation |
+ source, and configuration files. |
+ |
+ "Object" form shall mean any form resulting from mechanical |
+ transformation or translation of a Source form, including but |
+ not limited to compiled object code, generated documentation, |
+ and conversions to other media types. |
+ |
+ "Work" shall mean the work of authorship, whether in Source or |
+ Object form, made available under the License, as indicated by a |
+ copyright notice that is included in or attached to the work |
+ (an example is provided in the Appendix below). |
+ |
+ "Derivative Works" shall mean any work, whether in Source or Object |
+ form, that is based on (or derived from) the Work and for which the |
+ editorial revisions, annotations, elaborations, or other modifications |
+ represent, as a whole, an original work of authorship. For the purposes |
+ of this License, Derivative Works shall not include works that remain |
+ separable from, or merely link (or bind by name) to the interfaces of, |
+ the Work and Derivative Works thereof. |
+ |
+ "Contribution" shall mean any work of authorship, including |
+ the original version of the Work and any modifications or additions |
+ to that Work or Derivative Works thereof, that is intentionally |
+ submitted to Licensor for inclusion in the Work by the copyright owner |
+ or by an individual or Legal Entity authorized to submit on behalf of |
+ the copyright owner. For the purposes of this definition, "submitted" |
+ means any form of electronic, verbal, or written communication sent |
+ to the Licensor or its representatives, including but not limited to |
+ communication on electronic mailing lists, source code control systems, |
+ and issue tracking systems that are managed by, or on behalf of, the |
+ Licensor for the purpose of discussing and improving the Work, but |
+ excluding communication that is conspicuously marked or otherwise |
+ designated in writing by the copyright owner as "Not a Contribution." |
+ |
+ "Contributor" shall mean Licensor and any individual or Legal Entity |
+ on behalf of whom a Contribution has been received by Licensor and |
+ subsequently incorporated within the Work. |
+ |
+ 2. Grant of Copyright License. Subject to the terms and conditions of |
+ this License, each Contributor hereby grants to You a perpetual, |
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable |
+ copyright license to reproduce, prepare Derivative Works of, |
+ publicly display, publicly perform, sublicense, and distribute the |
+ Work and such Derivative Works in Source or Object form. |
+ |
+ 3. Grant of Patent License. Subject to the terms and conditions of |
+ this License, each Contributor hereby grants to You a perpetual, |
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable |
+ (except as stated in this section) patent license to make, have made, |
+ use, offer to sell, sell, import, and otherwise transfer the Work, |
+ where such license applies only to those patent claims licensable |
+ by such Contributor that are necessarily infringed by their |
+ Contribution(s) alone or by combination of their Contribution(s) |
+ with the Work to which such Contribution(s) was submitted. If You |
+ institute patent litigation against any entity (including a |
+ cross-claim or counterclaim in a lawsuit) alleging that the Work |
+ or a Contribution incorporated within the Work constitutes direct |
+ or contributory patent infringement, then any patent licenses |
+ granted to You under this License for that Work shall terminate |
+ as of the date such litigation is filed. |
+ |
+ 4. Redistribution. You may reproduce and distribute copies of the |
+ Work or Derivative Works thereof in any medium, with or without |
+ modifications, and in Source or Object form, provided that You |
+ meet the following conditions: |
+ |
+ (a) You must give any other recipients of the Work or |
+ Derivative Works a copy of this License; and |
+ |
+ (b) You must cause any modified files to carry prominent notices |
+ stating that You changed the files; and |
+ |
+ (c) You must retain, in the Source form of any Derivative Works |
+ that You distribute, all copyright, patent, trademark, and |
+ attribution notices from the Source form of the Work, |
+ excluding those notices that do not pertain to any part of |
+ the Derivative Works; and |
+ |
+ (d) If the Work includes a "NOTICE" text file as part of its |
+ distribution, then any Derivative Works that You distribute must |
+ include a readable copy of the attribution notices contained |
+ within such NOTICE file, excluding those notices that do not |
+ pertain to any part of the Derivative Works, in at least one |
+ of the following places: within a NOTICE text file distributed |
+ as part of the Derivative Works; within the Source form or |
+ documentation, if provided along with the Derivative Works; or, |
+ within a display generated by the Derivative Works, if and |
+ wherever such third-party notices normally appear. The contents |
+ of the NOTICE file are for informational purposes only and |
+ do not modify the License. You may add Your own attribution |
+ notices within Derivative Works that You distribute, alongside |
+ or as an addendum to the NOTICE text from the Work, provided |
+ that such additional attribution notices cannot be construed |
+ as modifying the License. |
+ |
+ You may add Your own copyright statement to Your modifications and |
+ may provide additional or different license terms and conditions |
+ for use, reproduction, or distribution of Your modifications, or |
+ for any such Derivative Works as a whole, provided Your use, |
+ reproduction, and distribution of the Work otherwise complies with |
+ the conditions stated in this License. |
+ |
+ 5. Submission of Contributions. Unless You explicitly state otherwise, |
+ any Contribution intentionally submitted for inclusion in the Work |
+ by You to the Licensor shall be under the terms and conditions of |
+ this License, without any additional terms or conditions. |
+ Notwithstanding the above, nothing herein shall supersede or modify |
+ the terms of any separate license agreement you may have executed |
+ with Licensor regarding such Contributions. |
+ |
+ 6. Trademarks. This License does not grant permission to use the trade |
+ names, trademarks, service marks, or product names of the Licensor, |
+ except as required for reasonable and customary use in describing the |
+ origin of the Work and reproducing the content of the NOTICE file. |
+ |
+ 7. Disclaimer of Warranty. Unless required by applicable law or |
+ agreed to in writing, Licensor provides the Work (and each |
+ Contributor provides its Contributions) on an "AS IS" BASIS, |
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or |
+ implied, including, without limitation, any warranties or conditions |
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A |
+ PARTICULAR PURPOSE. You are solely responsible for determining the |
+ appropriateness of using or redistributing the Work and assume any |
+ risks associated with Your exercise of permissions under this License. |
+ |
+ 8. Limitation of Liability. In no event and under no legal theory, |
+ whether in tort (including negligence), contract, or otherwise, |
+ unless required by applicable law (such as deliberate and grossly |
+ negligent acts) or agreed to in writing, shall any Contributor be |
+ liable to You for damages, including any direct, indirect, special, |
+ incidental, or consequential damages of any character arising as a |
+ result of this License or out of the use or inability to use the |
+ Work (including but not limited to damages for loss of goodwill, |
+ work stoppage, computer failure or malfunction, or any and all |
+ other commercial damages or losses), even if such Contributor |
+ has been advised of the possibility of such damages. |
+ |
+ 9. Accepting Warranty or Additional Liability. While redistributing |
+ the Work or Derivative Works thereof, You may choose to offer, |
+ and charge a fee for, acceptance of support, warranty, indemnity, |
+ or other liability obligations and/or rights consistent with this |
+ License. However, in accepting such obligations, You may act only |
+ on Your own behalf and on Your sole responsibility, not on behalf |
+ of any other Contributor, and only if You agree to indemnify, |
+ defend, and hold each Contributor harmless for any liability |
+ incurred by, or claims asserted against, such Contributor by reason |
+ of your accepting any such warranty or additional liability. |
+ |
+ END OF TERMS AND CONDITIONS |
+ |
+ APPENDIX: How to apply the Apache License to your work. |
+ |
+ To apply the Apache License to your work, attach the following |
+ boilerplate notice, with the fields enclosed by brackets "[]" |
+ replaced with your own identifying information. (Don't include |
+ the brackets!) The text should be enclosed in the appropriate |
+ comment syntax for the file format. We also recommend that a |
+ file or class name and description of purpose be included on the |
+ same "printed page" as the copyright notice for easier |
+ identification within third-party archives. |
+ |
+ Copyright [yyyy] [name of copyright owner] |
+ |
+ Licensed under the Apache License, Version 2.0 (the "License"); |
+ you may not use this file except in compliance with the License. |
+ You may obtain a copy of the License at |
+ |
+ http://www.apache.org/licenses/LICENSE-2.0 |
+ |
+ Unless required by applicable law or agreed to in writing, software |
+ distributed under the License is distributed on an "AS IS" BASIS, |
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
+ See the License for the specific language governing permissions and |
+ limitations under the License. |
+ |
+ |
+The Debian packaging is (C) 2007, Magnus Holmgren <magnus@kibibyte.se> and |
+is, for the sake of simplicity, licensed under the same license. |
Index: tags/1.0.19-1/debian/aclocal.m4 |
=================================================================== |
--- tags/1.0.19-1/debian/aclocal.m4 (nonexistent) |
+++ tags/1.0.19-1/debian/aclocal.m4 (revision 27) |
@@ -0,0 +1,171 @@ |
+# generated automatically by aclocal 1.9.6 -*- Autoconf -*- |
+ |
+# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, |
+# 2005 Free Software Foundation, Inc. |
+# This file is free software; the Free Software Foundation |
+# gives unlimited permission to copy and/or distribute it, |
+# with or without modifications, as long as this notice is preserved. |
+ |
+# This program is distributed in the hope that it will be useful, |
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without |
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A |
+# PARTICULAR PURPOSE. |
+ |
+# pkg.m4 - Macros to locate and utilise pkg-config. -*- Autoconf -*- |
+# |
+# Copyright © 2004 Scott James Remnant <scott@netsplit.com>. |
+# |
+# This program is free software; you can redistribute it and/or modify |
+# it under the terms of the GNU General Public License as published by |
+# the Free Software Foundation; either version 2 of the License, or |
+# (at your option) any later version. |
+# |
+# This program is distributed in the hope that it will be useful, but |
+# WITHOUT ANY WARRANTY; without even the implied warranty of |
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU |
+# General Public License for more details. |
+# |
+# You should have received a copy of the GNU General Public License |
+# along with this program; if not, write to the Free Software |
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. |
+# |
+# As a special exception to the GNU General Public License, if you |
+# distribute this file as part of a program that contains a |
+# configuration script generated by Autoconf, you may include it under |
+# the same distribution terms that you use for the rest of that program. |
+ |
+# PKG_PROG_PKG_CONFIG([MIN-VERSION]) |
+# ---------------------------------- |
+AC_DEFUN([PKG_PROG_PKG_CONFIG], |
+[m4_pattern_forbid([^_?PKG_[A-Z_]+$]) |
+m4_pattern_allow([^PKG_CONFIG(_PATH)?$]) |
+AC_ARG_VAR([PKG_CONFIG], [path to pkg-config utility])dnl |
+if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then |
+ AC_PATH_TOOL([PKG_CONFIG], [pkg-config]) |
+fi |
+if test -n "$PKG_CONFIG"; then |
+ _pkg_min_version=m4_default([$1], [0.9.0]) |
+ AC_MSG_CHECKING([pkg-config is at least version $_pkg_min_version]) |
+ if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then |
+ AC_MSG_RESULT([yes]) |
+ else |
+ AC_MSG_RESULT([no]) |
+ PKG_CONFIG="" |
+ fi |
+ |
+fi[]dnl |
+])# PKG_PROG_PKG_CONFIG |
+ |
+# PKG_CHECK_EXISTS(MODULES, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND]) |
+# |
+# Check to see whether a particular set of modules exists. Similar |
+# to PKG_CHECK_MODULES(), but does not set variables or print errors. |
+# |
+# |
+# Similar to PKG_CHECK_MODULES, make sure that the first instance of |
+# this or PKG_CHECK_MODULES is called, or make sure to call |
+# PKG_CHECK_EXISTS manually |
+# -------------------------------------------------------------- |
+AC_DEFUN([PKG_CHECK_EXISTS], |
+[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl |
+if test -n "$PKG_CONFIG" && \ |
+ AC_RUN_LOG([$PKG_CONFIG --exists --print-errors "$1"]); then |
+ m4_ifval([$2], [$2], [:]) |
+m4_ifvaln([$3], [else |
+ $3])dnl |
+fi]) |
+ |
+ |
+# _PKG_CONFIG([VARIABLE], [COMMAND], [MODULES]) |
+# --------------------------------------------- |
+m4_define([_PKG_CONFIG], |
+[if test -n "$PKG_CONFIG"; then |
+ if test -n "$$1"; then |
+ pkg_cv_[]$1="$$1" |
+ else |
+ PKG_CHECK_EXISTS([$3], |
+ [pkg_cv_[]$1=`$PKG_CONFIG --[]$2 "$3" 2>/dev/null`], |
+ [pkg_failed=yes]) |
+ fi |
+else |
+ pkg_failed=untried |
+fi[]dnl |
+])# _PKG_CONFIG |
+ |
+# _PKG_SHORT_ERRORS_SUPPORTED |
+# ----------------------------- |
+AC_DEFUN([_PKG_SHORT_ERRORS_SUPPORTED], |
+[AC_REQUIRE([PKG_PROG_PKG_CONFIG]) |
+if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then |
+ _pkg_short_errors_supported=yes |
+else |
+ _pkg_short_errors_supported=no |
+fi[]dnl |
+])# _PKG_SHORT_ERRORS_SUPPORTED |
+ |
+ |
+# PKG_CHECK_MODULES(VARIABLE-PREFIX, MODULES, [ACTION-IF-FOUND], |
+# [ACTION-IF-NOT-FOUND]) |
+# |
+# |
+# Note that if there is a possibility the first call to |
+# PKG_CHECK_MODULES might not happen, you should be sure to include an |
+# explicit call to PKG_PROG_PKG_CONFIG in your configure.ac |
+# |
+# |
+# -------------------------------------------------------------- |
+AC_DEFUN([PKG_CHECK_MODULES], |
+[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl |
+AC_ARG_VAR([$1][_CFLAGS], [C compiler flags for $1, overriding pkg-config])dnl |
+AC_ARG_VAR([$1][_LIBS], [linker flags for $1, overriding pkg-config])dnl |
+ |
+pkg_failed=no |
+AC_MSG_CHECKING([for $1]) |
+ |
+_PKG_CONFIG([$1][_CFLAGS], [cflags], [$2]) |
+_PKG_CONFIG([$1][_LIBS], [libs], [$2]) |
+ |
+m4_define([_PKG_TEXT], [Alternatively, you may set the environment variables $1[]_CFLAGS |
+and $1[]_LIBS to avoid the need to call pkg-config. |
+See the pkg-config man page for more details.]) |
+ |
+if test $pkg_failed = yes; then |
+ _PKG_SHORT_ERRORS_SUPPORTED |
+ if test $_pkg_short_errors_supported = yes; then |
+ $1[]_PKG_ERRORS=`$PKG_CONFIG --short-errors --errors-to-stdout --print-errors "$2"` |
+ else |
+ $1[]_PKG_ERRORS=`$PKG_CONFIG --errors-to-stdout --print-errors "$2"` |
+ fi |
+ # Put the nasty error message in config.log where it belongs |
+ echo "$$1[]_PKG_ERRORS" >&AS_MESSAGE_LOG_FD |
+ |
+ ifelse([$4], , [AC_MSG_ERROR(dnl |
+[Package requirements ($2) were not met: |
+ |
+$$1_PKG_ERRORS |
+ |
+Consider adjusting the PKG_CONFIG_PATH environment variable if you |
+installed software in a non-standard prefix. |
+ |
+_PKG_TEXT |
+])], |
+ [AC_MSG_RESULT([no]) |
+ $4]) |
+elif test $pkg_failed = untried; then |
+ ifelse([$4], , [AC_MSG_FAILURE(dnl |
+[The pkg-config script could not be found or is too old. Make sure it |
+is in your PATH or set the PKG_CONFIG environment variable to the full |
+path to pkg-config. |
+ |
+_PKG_TEXT |
+ |
+To get pkg-config, see <http://www.freedesktop.org/software/pkgconfig>.])], |
+ [$4]) |
+else |
+ $1[]_CFLAGS=$pkg_cv_[]$1[]_CFLAGS |
+ $1[]_LIBS=$pkg_cv_[]$1[]_LIBS |
+ AC_MSG_RESULT([yes]) |
+ ifelse([$3], , :, [$3]) |
+fi[]dnl |
+])# PKG_CHECK_MODULES |
+ |
Index: tags/1.0.19-1/debian/examples |
=================================================================== |
--- tags/1.0.19-1/debian/examples (nonexistent) |
+++ tags/1.0.19-1/debian/examples (revision 27) |
@@ -0,0 +1 @@ |
+src/libdkimtest.cpp |
Index: tags/1.0.19-1/debian/README.Debian |
=================================================================== |
--- tags/1.0.19-1/debian/README.Debian (nonexistent) |
+++ tags/1.0.19-1/debian/README.Debian (revision 27) |
@@ -0,0 +1,15 @@ |
+Yahoo! Inc. claims patent rights concerning DomainKeys and |
+DKIM. Details of the claim can be found at |
+<https://datatracker.ietf.org/public/ipr_detail_show.cgi?&ipr_id=693>. |
+Their licensing statement from that page reads as follows, as of |
+2007-02-30: |
+ |
+"Yahoo! licenses its Necessary Patent Claims contained in the patent(s) and |
+patent application(s) disclosed above under either of two separate license |
+agreements, one of which is the DomainKeys Patent License Agreement (v1.2), and |
+the other is the GNU General Public License v2.0 (and no other version)." |
+ |
+It is believed that this will cause normal users no legal problems, but the |
+packager can't guarantee anything. |
+ |
+For more information about DKIM, see http://mipassoc.org/dkim/ |
Index: tags/1.0.19-1/debian |
=================================================================== |
--- tags/1.0.19-1/debian (nonexistent) |
+++ tags/1.0.19-1/debian (revision 27) |
/tags/1.0.19-1/debian |
---|
Property changes: |
Added: mergeWithUpstream |
## -0,0 +1 ## |
+1 |
\ No newline at end of property |