diff options
Diffstat (limited to 'debian')
-rw-r--r-- | debian/.svnignore | 4 | ||||
-rw-r--r-- | debian/changelog | 46 | ||||
-rw-r--r-- | debian/compat | 1 | ||||
-rw-r--r-- | debian/control | 61 | ||||
-rw-r--r-- | debian/copyright | 507 | ||||
-rw-r--r-- | debian/docs | 3 | ||||
-rw-r--r-- | debian/libical-dev.install | 8 | ||||
-rw-r--r-- | debian/libical0.install | 1 | ||||
-rw-r--r-- | debian/python-libical.install | 1 | ||||
-rwxr-xr-x | debian/rules | 190 |
10 files changed, 822 insertions, 0 deletions
diff --git a/debian/.svnignore b/debian/.svnignore new file mode 100644 index 00000000..347a783a --- /dev/null +++ b/debian/.svnignore @@ -0,0 +1,4 @@ +libical-dev +libical0 +libical0-dbg +tmp diff --git a/debian/changelog b/debian/changelog new file mode 100644 index 00000000..aeae6c09 --- /dev/null +++ b/debian/changelog @@ -0,0 +1,46 @@ +libical (0.43-6) stable; urgency=high + + * new upstream release + + -- Wilfried Goesgens <w.goesgens@outgesourced.org> Sat, 13 Sep 2008 10:00:00 +0001 + +libical (0.31-4) stable; urgency=high + + * new release fixing a crash + + -- Wilfried Goesgens <w.goesgens@outgesourced.org> Mon, 17 Mar 2008 20:00:00 +0001 + +libical (0.30-1) unstable; urgency=low + +[ Wilfried Goesgens ] + * remove CDBS + * merge into upstream libical + * merge in several patches roaming arround + + -- Wilfried Goesgens <w.goesgens@outgesourced.org> Wed, 30 Nov 2007 12:19:06 +0100 + +libical (0.26.6-1) unstable; urgency=low + + [ Fathi Boudra ] + * Initial Debian release (Closes: #404862) + * Remove dirs and README.Debian + * Add soname patch + * compat: bumped to 5 + * control: + * convert package to cdbs + * add myself as uploader + * bump Standards-Version to 3.7.2 + * rewrite descriptions + * copyright: complete rewrite + + [ Wilfried Goesgens ] + * Update to aurore ical. + + -- Fathi Boudra <fboudra@free.fr> Wed, 27 Dec 2006 12:19:06 +0100 + +libical (0.24-1) unstable; urgency=low + + * Initial release + + -- Wilfried Goesgens <w.goesgens@outgesourced.org> Fri, 22 Jul 2005 13:09:43 +0200 + diff --git a/debian/compat b/debian/compat new file mode 100644 index 00000000..7ed6ff82 --- /dev/null +++ b/debian/compat @@ -0,0 +1 @@ +5 diff --git a/debian/control b/debian/control new file mode 100644 index 00000000..7a1022c7 --- /dev/null +++ b/debian/control @@ -0,0 +1,61 @@ +Source: libical +Section: libs +Priority: optional +Maintainer: Wilfried Goesgens <w.goesgens@outgesourced.org> +Uploaders: Fathi Boudra <fabo@debian.org> +Build-Depends: debhelper (>= 5.0.42), autotools-dev, tzdata, swig, + python-all-dev (>= 2.4.4), python-support (>= 0.5.6), python (>= 2.4.4) +XS-Python-Version: all +Standards-Version: 3.7.2 +Homepage: http://freeassociation.sourceforge.net + +Package: libical-dev +Section: libdevel +Architecture: any +Depends: ${misc:Depends}, libical0 (= ${binary:Version}) +Description: iCalendar library implementation in C (development) + libical is an open source implementation of the IETF's iCalendar calendaring + and scheduling protocols (RFC 2445, 2446, and 2447). It parses iCal components + and provides a C API for manipulating the component properties, parameters, + and subcomponents. + . + This package contains the libical development files. + +Package: libical0 +Section: libs +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends}, tzdata +Description: iCalendar library implementation in C (runtime) + libical is an open source implementation of the IETF's iCalendar calendaring + and scheduling protocols (RFC 2445, 2446, and 2447). It parses iCal components + and provides a C API for manipulating the component properties, parameters, + and subcomponents. + . + This package contains the files necessary for running applications that use + the libical library. + +Package: libical0-dbg +Section: libs +Priority: extra +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends}, libical0 (= ${binary:Version}) +Description: iCalendar library implementation in C (runtime) + libical is an open source implementation of the IETF's iCalendar calendaring + and scheduling protocols (RFC 2445, 2446, and 2447). It parses iCal components + and provides a C API for manipulating the component properties, parameters, + and subcomponents. + . + This package contains the files necessary for running and debugging + applications that use the libical library. + +Package: python-libical +Section: python +Architecture: any +Depends: ${shlibs:Depends}, ${python:Depends}, libical0 (= ${binary:Version}) +Description: iCalendar library implementation python language bindings + libical is an open source implementation of the IETF's iCalendar calendaring + and scheduling protocols (RFC 2445, 2446, and 2447). It parses iCal components + and provides a C API for manipulating the component properties, parameters, + and subcomponents. + . + This package contains the python language bindings. diff --git a/debian/copyright b/debian/copyright new file mode 100644 index 00000000..9f0bec16 --- /dev/null +++ b/debian/copyright @@ -0,0 +1,507 @@ +This package was debianized by Fathi Boudra <fboudra@free.fr> on +Wed, 27 Dec 2006 12:19:06 +0100. + +It was downloaded from http://www.aurore.net/projects/libical/ + +This is a modified version of the original libical project from softwarestudio +and the original author is Eric Busboom <eric@softwarestudio.org>. + +Upstream Authors: + John Gray <gray@agora-net.com> + Andrea Campi <a.campi@inet.it> + Omar Kilani <omar@tinysofa.org> + +Copyright for generated icalderivedproperties: + (C) 1999 Eric Busboom <eric@softwarestudio.org> + +Copyright for generated restrictionrecords and parameterrestrictions: + (C) 1999 Graham Davison <g.m.davison@computer.org> + +Copyright for sspm based on code from the mimelite distribution: + (C) 1994 Gisle Hannemyr <gisle@oslonett.no> + (C) 2000 Eric Busboom <eric@softwarestudio.org> + +Copyright for snprintf: + (C) 1997 Theo de Raadt + +Copyright for astime and caldate: + (C) 1986-2000 Hiram Clawson + +Copyright for icalattach: + (C) 2002 Andrea Campi <a.campi@inet.it> + +Copyright for icaltimezone: + (C) 2001 Damon Chaplin + +Copyright for icalarray: + (C) 2001 Ximian Inc. + +astime and caldate license: + + Redistribution and use in source and binary forms, with or + without modification, are permitted provided that the following + conditions are met: + + Redistributions of source code must retain the above + copyright notice, this list of conditions and the + following disclaimer. + + Redistributions in binary form must reproduce the + above copyright notice, this list of conditions and + the following disclaimer in the documentation and/or + other materials provided with the distribution. + + Neither name of The Museum of Hiram nor the names of + its contributors may be used to endorse or promote products + derived from this software without specific prior + written permission. + + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND + CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, + INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF + MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. + IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + 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 USE OF THIS SOFTWARE, EVEN IF ADVISED OF + THE POSSIBILITY OF SUCH DAMAGE. + +snprintf license: + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + + THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR + IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. + IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT + NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, + DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 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 USE OF + THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +sspm license: + + Permission is granted to hack, make and distribute copies of this + program as long as this copyright notice is not removed. + +libical license: + +The code and datafiles in this distribution are licensed under the +Mozilla Public License. See http://www.mozilla.org/NPL/MPL-1.0.html +for a copy of the license. Alternately, you may use libical under the +terms of the GNU Library General Public License. See +http://www.fsf.org/copyleft/lesser.html for a copy of the LGPL. + +This dual license ensures that the library can be incorporated into +both proprietary code and GPL'd programs, and will benefit from +improvements made by programmers in both realms. I will only accept +changes into my version of the library if they are similarly +dual-licensed. + + This program is free software; you can redistribute it and/or modify + it under the terms of either: + + The LGPL as published by the Free Software Foundation, version + 2.1, available at: http://www.fsf.org/copyleft/lesser.html + + Or: + + The Mozilla Public License Version 1.0. You may obtain a copy of + the License at http://www.mozilla.org/MPL/ + +MPL 1.0 license: + + MOZILLA PUBLIC LICENSE + Version 1.0 + + ---------------- + +1. Definitions. + + 1.1. ``Contributor'' means each entity that creates or contributes to + the creation of Modifications. + + 1.2. ``Contributor Version'' means the combination of the Original + Code, prior Modifications used by a Contributor, and the Modifications + made by that particular Contributor. + + 1.3. ``Covered Code'' means the Original Code or Modifications or the + combination of the Original Code and Modifications, in each case + including portions thereof. + + 1.4. ``Electronic Distribution Mechanism'' means a mechanism generally + accepted in the software development community for the electronic + transfer of data. + + 1.5. ``Executable'' means Covered Code in any form other than Source + Code. + + 1.6. ``Initial Developer'' means the individual or entity identified as + the Initial Developer in the Source Code notice required by Exhibit A. + + 1.7. ``Larger Work'' means a work which combines Covered Code or + portions thereof with code not governed by the terms of this License. + + 1.8. ``License'' means this document. + + 1.9. ``Modifications'' means any addition to or deletion from the + substance or structure of either the Original Code or any previous + Modifications. When Covered Code is released as a series of files, a + Modification is: + + A. Any addition to or deletion from the contents of a file + containing Original Code or previous Modifications. + + B. Any new file that contains any part of the Original Code or + previous Modifications. + + 1.10. ``Original Code'' means Source Code of computer software code + which is described in the Source Code notice required by Exhibit A as + Original Code, and which, at the time of its release under this License + is not already Covered Code governed by this License. + + 1.11. ``Source Code'' means the preferred form of the Covered Code for + making modifications to it, including all modules it contains, plus any + associated interface definition files, scripts used to control + compilation and installation of an Executable, or a list of source code + differential comparisons against either the Original Code or another + well known, available Covered Code of the Contributor's choice. The + Source Code can be in a compressed or archival form, provided the + appropriate decompression or de-archiving software is widely available + for no charge. + + 1.12. ``You'' means an individual or a legal entity exercising rights + under, and complying with all of the terms of, this License or a future + version of this License issued under Section 6.1. For legal entities, + ``You'' includes any entity which controls, is controlled by, or is + under common control with You. For purposes of this definition, + ``control'' means (a) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (b) ownership of fifty percent (50%) or more of the + outstanding shares or beneficial ownership of such entity. + +2. Source Code License. + + 2.1. The Initial Developer Grant. + The Initial Developer hereby grants You a world-wide, royalty-free, + non-exclusive license, subject to third party intellectual property + claims: + + (a) to use, reproduce, modify, display, perform, sublicense and + distribute the Original Code (or portions thereof) with or without + Modifications, or as part of a Larger Work; and + + (b) under patents now or hereafter owned or controlled by Initial + Developer, to make, have made, use and sell (``Utilize'') the + Original Code (or portions thereof), but solely to the extent that + any such patent is reasonably necessary to enable You to Utilize + the Original Code (or portions thereof) and not to any greater + extent that may be necessary to Utilize further Modifications or + combinations. + + 2.2. Contributor Grant. + Each Contributor hereby grants You a world-wide, royalty-free, + non-exclusive license, subject to third party intellectual property + claims: + + (a) to use, reproduce, modify, display, perform, sublicense and + distribute the Modifications created by such Contributor (or + portions thereof) either on an unmodified basis, with other + Modifications, as Covered Code or as part of a Larger Work; and + + (b) under patents now or hereafter owned or controlled by + Contributor, to Utilize the Contributor Version (or portions + thereof), but solely to the extent that any such patent is + reasonably necessary to enable You to Utilize the Contributor + Version (or portions thereof), and not to any greater extent that + may be necessary to Utilize further Modifications or combinations. + +3. Distribution Obligations. + + 3.1. Application of License. + The Modifications which You create or to which You contribute are + governed by the terms of this License, including without limitation + Section 2.2. The Source Code version of Covered Code may be distributed + only under the terms of this License or a future version of this + License released under Section 6.1, and You must include a copy of this + License with every copy of the Source Code You distribute. You may not + offer or impose any terms on any Source Code version that alters or + restricts the applicable version of this License or the recipients' + rights hereunder. However, You may include an additional document + offering the additional rights described in Section 3.5. + + 3.2. Availability of Source Code. + Any Modification which You create or to which You contribute must be + made available in Source Code form under the terms of this License + either on the same media as an Executable version or via an accepted + Electronic Distribution Mechanism to anyone to whom you made an + Executable version available; and if made available via Electronic + Distribution Mechanism, must remain available for at least twelve (12) + months after the date it initially became available, or at least six + (6) months after a subsequent version of that particular Modification + has been made available to such recipients. You are responsible for + ensuring that the Source Code version remains available even if the + Electronic Distribution Mechanism is maintained by a third party. + + 3.3. Description of Modifications. + You must cause all Covered Code to which you contribute to contain a + file documenting the changes You made to create that Covered Code and + the date of any change. You must include a prominent statement that the + Modification is derived, directly or indirectly, from Original Code + provided by the Initial Developer and including the name of the Initial + Developer in (a) the Source Code, and (b) in any notice in an + Executable version or related documentation in which You describe the + origin or ownership of the Covered Code. + + 3.4. Intellectual Property Matters + + (a) Third Party Claims. + If You have knowledge that a party claims an intellectual property + right in particular functionality or code (or its utilization + under this License), you must include a text file with the source + code distribution titled ``LEGAL'' which describes the claim and + the party making the claim in sufficient detail that a recipient + will know whom to contact. If you obtain such knowledge after You + make Your Modification available as described in Section 3.2, You + shall promptly modify the LEGAL file in all copies You make + available thereafter and shall take other steps (such as notifying + appropriate mailing lists or newsgroups) reasonably calculated to + inform those who received the Covered Code that new knowledge has + been obtained. + + (b) Contributor APIs. + If Your Modification is an application programming interface and + You own or control patents which are reasonably necessary to + implement that API, you must also include this information in the + LEGAL file. + + 3.5. Required Notices. + You must duplicate the notice in Exhibit A in each file of the Source + Code, and this License in any documentation for the Source Code, where + You describe recipients' rights relating to Covered Code. If You + created one or more Modification(s), You may add your name as a + Contributor to the notice described in Exhibit A. If it is not possible + to put such notice in a particular Source Code file due to its + structure, then you must include such notice in a location (such as a + relevant directory file) where a user would be likely to look for such + a notice. You may choose to offer, and to charge a fee for, warranty, + support, indemnity or liability obligations to one or more recipients + of Covered Code. However, You may do so only on Your own behalf, and + not on behalf of the Initial Developer or any Contributor. You must + make it absolutely clear than any such warranty, support, indemnity or + liability obligation is offered by You alone, and You hereby agree to + indemnify the Initial Developer and every Contributor for any liability + incurred by the Initial Developer or such Contributor as a result of + warranty, support, indemnity or liability terms You offer. + + 3.6. Distribution of Executable Versions. + You may distribute Covered Code in Executable form only if the + requirements of Section 3.1-3.5 have been met for that Covered Code, + and if You include a notice stating that the Source Code version of the + Covered Code is available under the terms of this License, including a + description of how and where You have fulfilled the obligations of + Section 3.2. The notice must be conspicuously included in any notice in + an Executable version, related documentation or collateral in which You + describe recipients' rights relating to the Covered Code. You may + distribute the Executable version of Covered Code under a license of + Your choice, which may contain terms different from this License, + provided that You are in compliance with the terms of this License and + that the license for the Executable version does not attempt to limit + or alter the recipient's rights in the Source Code version from the + rights set forth in this License. If You distribute the Executable + version under a different license You must make it absolutely clear + that any terms which differ from this License are offered by You alone, + not by the Initial Developer or any Contributor. You hereby agree to + indemnify the Initial Developer and every Contributor for any liability + incurred by the Initial Developer or such Contributor as a result of + any such terms You offer. + + 3.7. Larger Works. + You may create a Larger Work by combining Covered Code with other code + not governed by the terms of this License and distribute the Larger + Work as a single product. In such a case, You must make sure the + requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. + + If it is impossible for You to comply with any of the terms of this + License with respect to some or all of the Covered Code due to statute + or regulation then You must: (a) comply with the terms of this License + to the maximum extent possible; and (b) describe the limitations and + the code they affect. Such description must be included in the LEGAL + file described in Section 3.4 and must be included with all + distributions of the Source Code. Except to the extent prohibited by + statute or regulation, such description must be sufficiently detailed + for a recipient of ordinary skill to be able to understand it. + +5. Application of this License. + + This License applies to code to which the Initial Developer has + attached the notice in Exhibit A, and to related Covered Code. + +6. Versions of the License. + + 6.1. New Versions. + Netscape Communications Corporation (``Netscape'') may publish revised + and/or new versions of the License from time to time. Each version will + be given a distinguishing version number. + + 6.2. Effect of New Versions. + Once Covered Code has been published under a particular version of the + License, You may always continue to use it under the terms of that + version. You may also choose to use such Covered Code under the terms + of any subsequent version of the License published by Netscape. No one + other than Netscape has the right to modify the terms applicable to + Covered Code created under this License. + + 6.3. Derivative Works. + If you create or use a modified version of this License (which you may + only do in order to apply it to code which is not already Covered Code + governed by this License), you must (a) rename Your license so that the + phrases ``Mozilla'', ``MOZILLAPL'', ``MOZPL'', ``Netscape'', ``NPL'' or + any confusingly similar phrase do not appear anywhere in your license + and (b) otherwise make it clear that your version of the license + contains terms which differ from the Mozilla Public License and + Netscape Public License. (Filling in the name of the Initial Developer, + Original Code or Contributor in the notice described in Exhibit A shall + not of themselves be deemed to be modifications of this License.) + +7. DISCLAIMER OF WARRANTY. + + COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, + WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF + DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. + THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE + IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE + COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF + ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. + + This License and the rights granted hereunder will terminate + automatically if You fail to comply with terms herein and fail to cure + such breach within 30 days of becoming aware of the breach. All + sublicenses to the Covered Code which are properly granted shall + survive any termination of this License. Provisions which, by their + nature, must remain in effect beyond the termination of this License + shall survive. + +9. LIMITATION OF LIABILITY. + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT + (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL + DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, + OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER + PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES + OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF + GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND + ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE + BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF + LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY + RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW + PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE + EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT + EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. + +10. U.S. GOVERNMENT END USERS. + + The Covered Code is a ``commercial item,'' as that term is defined in + 48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer + software'' and ``commercial computer software documentation,'' as such + terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 + C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), + all U.S. Government End Users acquire Covered Code with only those + rights set forth herein. + +11. MISCELLANEOUS. + + This License represents the complete agreement concerning subject + matter hereof. If any provision of this License is held to be + unenforceable, such provision shall be reformed only to the extent + necessary to make it enforceable. This License shall be governed by + California law provisions (except to the extent applicable law, if any, + provides otherwise), excluding its conflict-of-law provisions. With + respect to disputes in which at least one party is a citizen of, or an + entity chartered or registered to do business in, the United States of + America: (a) unless otherwise agreed in writing, all disputes relating + to this License (excepting any dispute relating to intellectual + property rights) shall be subject to final and binding arbitration, + with the losing party paying all costs of arbitration; (b) any + arbitration relating to this Agreement shall be held in Santa Clara + County, California, under the auspices of JAMS/EndDispute; and (c) any + litigation relating to this Agreement shall be subject to the + jurisdiction of the Federal Courts of the Northern District of + California, with venue lying in Santa Clara County, California, with + the losing party responsible for costs, including without limitation, + court costs and reasonable attorneys fees and expenses. The application + of the United Nations Convention on Contracts for the International + Sale of Goods is expressly excluded. Any law or regulation which + provides that the language of a contract shall be construed against the + drafter shall not apply to this License. + +12. RESPONSIBILITY FOR CLAIMS. + + Except in cases where another Contributor has failed to comply with + Section 3.4, You are responsible for damages arising, directly or + indirectly, out of Your utilization of rights under this License, based + on the number of copies of Covered Code you made available, the + revenues you received from utilizing such rights, and other relevant + factors. You agree to work with affected parties to distribute + responsibility on an equitable basis. + +EXHIBIT A. + + ``The contents of this file are subject to the Mozilla Public License + Version 1.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.mozilla.org/MPL/ + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the + License for the specific language governing rights and limitations + under the License. + + The Original Code is ______________________________________. + + The Initial Developer of the Original Code is ________________________. + Portions created by ______________________ are Copyright (C) ______ + _______________________. All Rights Reserved. + + Contributor(s): ______________________________________.'' + +LGPL license: + + This package is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2 of the License, or (at your option) any later version. + + This package 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 + Lesser General Public License for more details. + + You should have received a copy of the GNU Lesser General Public + License along with this package; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + +On Debian systems, the complete text of the GNU Lesser General +Public License can be found in `/usr/share/common-licenses/LGPL'. + +The Debian packaging is (C) 2006, Fathi Boudra <fboudra@free.fr> and +is licensed under the GPL, see `/usr/share/common-licenses/GPL'. diff --git a/debian/docs b/debian/docs new file mode 100644 index 00000000..5502ed8f --- /dev/null +++ b/debian/docs @@ -0,0 +1,3 @@ +NEWS +README +TODO diff --git a/debian/libical-dev.install b/debian/libical-dev.install new file mode 100644 index 00000000..a4048486 --- /dev/null +++ b/debian/libical-dev.install @@ -0,0 +1,8 @@ +usr/include +usr/lib/libical.a +usr/lib/libical.so +usr/lib/libicalss.a +usr/lib/libicalss.so +usr/lib/libicalvcal.a +usr/lib/libicalvcal.so +usr/lib/pkgconfig/libical.pc
\ No newline at end of file diff --git a/debian/libical0.install b/debian/libical0.install new file mode 100644 index 00000000..d0dbfd18 --- /dev/null +++ b/debian/libical0.install @@ -0,0 +1 @@ +usr/lib/lib*.so.* diff --git a/debian/python-libical.install b/debian/python-libical.install new file mode 100644 index 00000000..4c2a9a74 --- /dev/null +++ b/debian/python-libical.install @@ -0,0 +1 @@ +usr/lib/pymodules/*
\ No newline at end of file diff --git a/debian/rules b/debian/rules new file mode 100755 index 00000000..3e78ac9e --- /dev/null +++ b/debian/rules @@ -0,0 +1,190 @@ +#!/usr/bin/make -f + +# Uncomment this to turn on verbose mode. +#export DH_VERBOSE=1 + +# These are used for cross-compiling and for saving the configure script +# from having to guess our platform (since we know it already) +DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) +DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) + +CFLAGS = -Wall -g +EXTRA_ARGS= +PROFILE_ARGS= + +# To enable debugging: export DEB_BUILD_OPTIONS="debug profiling threadoff" +ifneq (,$(findstring profiling,$(DEB_BUILD_OPTIONS))) + PROFILE_ARGS= --with-gprof +endif + +ifneq (,$(findstring backtrace,$(DEB_BUILD_OPTIONS))) + EXTRA_ARGS=--with-backtrace + BTCFLAGS=-rdynamic +endif + +ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS))) + CFLAGS += -O0 -ggdb -D_GNU_SOURCE -MD -MP -Wl,--as-needed -Wall -ansi +else + CFLAGS += -O2 +endif + +# shared library versions, option 1 +version=2.0.5 +major=2 +# option 2, assuming the library is created as src/.libs/libfoo.so.2.0.5 or so +#version=`ls src/.libs/lib*.so.* | \ +# awk '{if (match($$0,/[0-9]+\.[0-9]+\.[0-9]+$$/)) print substr($$0,RSTART)}'` +#major=`ls src/.libs/lib*.so.* | \ +# awk '{if (match($$0,/\.so\.[0-9]+$$/)) print substr($$0,RSTART+4)}'` + +PYVERS=$(shell pyversions -vr) + +build: build-c $(PYVERS:%=build-python%/build-stamp) +install: build install-c $(PYVERS:%=install-python%) +clean: clean-c $(PYVERS:%=clean-python%) + +### Python libraries build rules ### +build-python%/configure-stamp: + dh_testdir + + mkdir build-python$* + cd build-python$* && \ + PYTHON=/usr/bin/python$* CFLAGS="$(BTCFLAGS) $(CFLAGS)" ../configure \ + --host=$(DEB_HOST_GNU_TYPE) \ + --build=$(DEB_BUILD_GNU_TYPE) \ + --srcdir=.. \ + --prefix=/usr \ + --includedir="/usr/include" \ + --mandir="/usr/share/man" \ + --sysconfdir=/etc \ + --localstatedir=/var \ + $(EXTRA_ARGS) $(PROFILE_ARGS) \ + --libexecdir="/usr/lib/libical" \ + --enable-python + touch $@ + +build-python%/build-stamp: build-c build-python%/configure-stamp + dh_testdir + + # Trick into using already built build-c libs so we don't end up + # building the same ical lib more than once. + find "build-python$*/src" -maxdepth 1 -mindepth 1 | grep -v python$$ | xargs -r -t rm -rf + find "build-c/src" -maxdepth 1 -mindepth 1 | grep -v python$$ | xargs -r -t -I{} ln -s "../../{}" "build-python$*/src" + + $(MAKE) -C build-python$*/src/python pyexecdir=/usr/lib/pymodules/python$* + + touch $@ + +install-python%: build-python%/build-stamp + dh_testdir + dh_testroot +# dh_clean -k + dh_installdirs + + # install with hack to move installed python libs to pymodule dir + $(MAKE) -C build-python$*/src/python install pyexecdir=/usr/lib/pymodules/python$* DESTDIR=$(CURDIR)/debian/tmp && \ + mv -i $(CURDIR)/debian/tmp/usr/lib/python$*/*/* $(CURDIR)/debian/tmp/usr/lib/pymodules/python$*/ + +clean-python%: +# mkdir -p build-python$* && cd build-python$* + dh_testdir +# dh_testroot + rm -rf build-python$* + dh_prep + +### C libraries build rules ### +build-c/configure-stamp: configure +#config.status: configure + dh_testdir + +ifneq "$(wildcard /usr/share/misc/config.sub)" "" + cp -f /usr/share/misc/config.sub config.sub +endif +ifneq "$(wildcard /usr/share/misc/config.guess)" "" + cp -f /usr/share/misc/config.guess config.guess +endif + + mkdir build-c + cd build-c && \ + CFLAGS="$(BTCFLAGS) $(CFLAGS)" ../configure \ + --host=$(DEB_HOST_GNU_TYPE) \ + --build=$(DEB_BUILD_GNU_TYPE) \ + --prefix=/usr \ + --includedir="/usr/include" \ + --mandir="/usr/share/man" \ + --sysconfdir=/etc \ + --localstatedir=/var \ + $(EXTRA_ARGS) $(PROFILE_ARGS) \ + --libexecdir="/usr/lib/libical" + + touch $@ + +build-c: build-c/build-stamp +build-c/build-stamp: build-c/configure-stamp + dh_testdir + +# $(MAKE) clean + $(MAKE) -C build-c + + touch $@ + +clean-c: + dh_testdir + dh_testroot + + rm -rf build-c + + dh_prep + +install-c: build-c + dh_testdir + dh_testroot + dh_clean -k + dh_installdirs + + $(MAKE) -C build-c DESTDIR=$(CURDIR)/debian/tmp install + +# 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_installchangelogs ChangeLog + dh_installdocs + dh_installexamples + dh_install -s --sourcedir=debian/tmp +# dh_installmenu +# dh_installdebconf +# dh_installlogrotate +# dh_installemacsen +# dh_installpam +# dh_installmime +# dh_installinit +# dh_installcron +# dh_installinfo + dh_installman + dh_link + dh_strip + dh_compress + dh_fixperms +# dh_perl + dh_pysupport +# dh_makeshlibs + dh_installdeb +# dh_shlibdeps + # We need to exclude dependency resolving for the python extension + # module because if libical0 is installed but libical-dev is not + # we get build errors. The lib in /usr/lib will be found first + # but no .la will exist to get the dependency info from. Is there + # a way to tell dh_shlibdeps to find the lib first in debian/tmp? + dh_shlibdeps -XLibicalWrap +# dh_shlibdeps -l$(CURDIR)/debian/tmp/usr/lib -- -v + dh_gencontrol + dh_md5sums + dh_builddeb + +binary: binary-indep binary-arch +.PHONY: build clean binary-indep binary-arch binary install |