[SCM] Packaging for tachyon branch, master, updated. debian/0.98.beta.dfsg-1-2-g4143635
Tobias Hansen
tobias.han at gmx.de
Mon Dec 17 22:36:11 UTC 2012
The following commit has been merged in the master branch:
commit 41436359cfe302025682f1fe4e358df681e73cbe
Merge: e5697cd6bef1cc30eeea55978a329bf6d41c25a4 30bb006c565cc0692db694320aef41133a534b75
Author: Steffen Moeller <moeller at debian.org>
Date: Tue Mar 29 13:37:53 2011 +0200
Imported Debian patch 0.99~b2+dfsg-0.1
diff --combined debian/README.source
index 0000000,0000000..fe25606
new file mode 100644
--- /dev/null
+++ b/debian/README.source
@@@ -1,0 -1,0 +1,8 @@@
++Tachyon
++=======
++
++ * Removed CVS directories
++ * Removed doc/*.sty except for doc/pdfdraftcopy.sty
++ * find . -name ".#*" | xargs -r rm
++
++Left in the msvc folder, which seems find copyright-wise.
diff --combined debian/changelog
index 901f6a3,0000000..37daf16
mode 100644,000000..100644
--- a/debian/changelog
+++ b/debian/changelog
@@@ -1,15 -1,0 +1,27 @@@
++tachyon (0.99~b2+dfsg-0.1) unstable; urgency=low
++
++ * Non-maintainer upload.
++ * New upstream version (Closes: #600938, #567997).
++ * Reassignment of lib package to section lib (Closes: #490014).
++ * Helped lintian cleanliness for BSD license warning.
++ * No CDBS debian/control management.
++ * Removed leading "../" from path in debian/patches/architecture.patch
++ * Added LaTeX license to debian/copyright as requested by FTPadmins
++
++ -- Steffen Moeller <moeller at debian.org> Tue, 29 Mar 2011 13:37:53 +0200
++
+tachyon (0.98~beta.dfsg-1) unstable; urgency=low
+
+ * Set priority to optional.
+ * Remove files generated by non-DFSG free latex2html.
+ * Update to Standards-Version 3.8.0.
+ * Create new linux-base-thr architecture for tachyon that doesn't assume
+ x86 and incorrectly include -m32 in CFLAGS (Closes: #486849).
+
+ -- Tim Abbott <tabbott at mit.edu> Fri, 20 Jun 2008 11:24:50 -0400
+
+tachyon (0.98~beta-1) unstable; urgency=low
+
+ * Initial release (Closes: #480082).
+
+ -- Tim Abbott <tabbott at mit.edu> Fri, 06 Jun 2008 18:28:02 -0400
diff --combined debian/control
index 829711f,0000000..3fec650
mode 100644,000000..100644
--- a/debian/control
+++ b/debian/control
@@@ -1,72 -1,0 +1,81 @@@
+Source: tachyon
+Section: math
+Priority: optional
+Maintainer: Tim Abbott <tabbott at mit.edu>
- Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5), quilt, patchutils (>= 0.2.25), cdbs (>= 0.4.27), libpng12-dev
- Standards-Version: 3.8.0
++Build-Depends: debhelper (>= 5), cdbs (>= 0.4.27), libpng12-dev
++Build-Depends-Indep: texlive-latex-recommended, texlive-science, texlive-latex-extra, texlive-humanities
++Standards-Version: 3.9.1
+
+Package: tachyon
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: Parallel/Multiprocessor Ray Tracing Software
+ Tachyon is a portable, high performance parallel ray tracing system
+ supporting MPI and multithreaded implementations. Tachyon is built
+ as a C callable library, which can be used with the included demo
+ programs or within your own application. The distribution also
+ includes a simple scene file parser front-end which reads a few
+ different formats.
+ .
+ Tachyon implements all of the basic geometric primitives such as
+ triangles, planes, spheres, cylinders, etc. Some of the goals in
+ developing Tachyon were to make it fast and for it to parallelize
+ well. These are what set it apart from more full-featured programs
+ like POV-Ray, Rayshade, and others. Tachyon supports enough features
+ to be an excellent alternative to slower programs for demanding
+ animation and scientific visualization tasks. As time goes on,
+ Tachyon will indeed incorporate more features, but with a continued
+ emphasis on rendering performance.
+
- Package: libtachyon-0.98
++Package: tachyon-doc
++Architecture: all
++Section: doc
++Depends: ${shlibs:Depends}, ${misc:Depends}
++Description: documentation for Tachyon ray tracer
++ The compilation of the LaTeX documentation demands the
++ installation of most components of texlive.
++
++Package: libtachyon-0.99
+Section: libs
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: Parallel/Multiprocessor Ray Tracing Software, shared library
+ Tachyon is a portable, high performance parallel ray tracing system
+ supporting MPI and multithreaded implementations. Tachyon is built
+ as a C callable library, which can be used with the included demo
+ programs or within your own application. The distribution also
+ includes a simple scene file parser front-end which reads a few
+ different formats.
+ .
+ Tachyon implements all of the basic geometric primitives such as
+ triangles, planes, spheres, cylinders, etc. Some of the goals in
+ developing Tachyon were to make it fast and for it to parallelize
+ well. These are what set it apart from more full-featured programs
+ like POV-Ray, Rayshade, and others. Tachyon supports enough features
+ to be an excellent alternative to slower programs for demanding
+ animation and scientific visualization tasks. As time goes on,
+ Tachyon will indeed incorporate more features, but with a continued
+ emphasis on rendering performance.
+
+Package: libtachyon-dev
+Section: libdevel
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: Parallel/Multiprocessor Ray Tracing Software, development files
+ Tachyon is a portable, high performance parallel ray tracing system
+ supporting MPI and multithreaded implementations. Tachyon is built
+ as a C callable library, which can be used with the included demo
+ programs or within your own application. The distribution also
+ includes a simple scene file parser front-end which reads a few
+ different formats.
+ .
+ Tachyon implements all of the basic geometric primitives such as
+ triangles, planes, spheres, cylinders, etc. Some of the goals in
+ developing Tachyon were to make it fast and for it to parallelize
+ well. These are what set it apart from more full-featured programs
+ like POV-Ray, Rayshade, and others. Tachyon supports enough features
+ to be an excellent alternative to slower programs for demanding
+ animation and scientific visualization tasks. As time goes on,
+ Tachyon will indeed incorporate more features, but with a continued
+ emphasis on rendering performance.
+
diff --combined debian/copyright
index c6ecf21,0000000..58fbf9f
mode 100644,000000..100644
--- a/debian/copyright
+++ b/debian/copyright
@@@ -1,36 -1,0 +1,493 @@@
+This package was debianized by Tim Abbott <tabbott at mit.edu> in 2008.
+
+It was downloaded from http://jedi.ks.uiuc.edu/~johns/raytracer/
+
++Files: *
++
+Upstream Authors: John E. Stone - johns at megapixel.com (preferred email address)
+ j.stone at acm.org (preferred email address)
+ johns at ks.uiuc.edu (work email address)
+Copyright:
+
+ Copyright (C) 1994-2008 John E. Stone
+
+License:
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted under the terms of the BSD License.
+
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS 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.
+
- On Debian systems, the complete text of the BSD License can be
- found in `/usr/share/common-licenses/BSD'.
++ and from the Copyright file
++
++ /*
++ * Copyright (c) 1994-2011 John E. Stone
++ * All rights reserved.
++ *
++ * 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.
++ * 3. The name of the author may not be used to endorse or promote products
++ * derived from this software without specific prior written permission.
++ *
++ * 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.
++ *
++ * $Id: Copyright,v 1.10 2011/02/05 18:56:09 johns Exp $
++ *
++ */
++
+
+The docs/tachyon directory and docs/tachyon.html.tar.gz have been
+removed because they were generated using the non-free latex2html.
+
++ Files: doc/pdfdraftcopy.sty
++ License:
++ This package may be distributed under the terms of the LaTeX Project
++ Public License, as described in lppl.txt in the base LaTeX distribution.
++ Either version 1.0 or, at your option, any later version.
++
++ The LaTeX Project Public License
++ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
++
++ LPPL Version 1.3c 2006-05-20
++
++ Copyright 1999 2002-2006 LaTeX3 Project
++ Everyone is allowed to distribute verbatim copies of this
++ license document, but modification of it is not allowed.
++
++
++ PREAMBLE
++ ========
++
++ The LaTeX Project Public License (LPPL) is the primary license under
++ which the the LaTeX kernel and the base LaTeX packages are distributed.
++
++ You may use this license for any work of which you hold the copyright
++ and which you wish to distribute. This license may be particularly
++ suitable if your work is TeX-related (such as a LaTeX package), but
++ it is written in such a way that you can use it even if your work is
++ unrelated to TeX.
++
++ The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
++ below, gives instructions, examples, and recommendations for authors
++ who are considering distributing their works under this license.
++
++ This license gives conditions under which a work may be distributed
++ and modified, as well as conditions under which modified versions of
++ that work may be distributed.
++
++ We, the LaTeX3 Project, believe that the conditions below give you
++ the freedom to make and distribute modified versions of your work
++ that conform with whatever technical specifications you wish while
++ maintaining the availability, integrity, and reliability of
++ that work. If you do not see how to achieve your goal while
++ meeting these conditions, then read the document `cfgguide.tex'
++ and `modguide.tex' in the base LaTeX distribution for suggestions.
++
++
++ DEFINITIONS
++ ===========
++
++ In this license document the following terms are used:
++
++ `Work'
++ Any work being distributed under this License.
++
++ `Derived Work'
++ Any work that under any applicable law is derived from the Work.
++
++ `Modification'
++ Any procedure that produces a Derived Work under any applicable
++ law -- for example, the production of a file containing an
++ original file associated with the Work or a significant portion of
++ such a file, either verbatim or with modifications and/or
++ translated into another language.
++
++ `Modify'
++ To apply any procedure that produces a Derived Work under any
++ applicable law.
++
++ `Distribution'
++ Making copies of the Work available from one person to another, in
++ whole or in part. Distribution includes (but is not limited to)
++ making any electronic components of the Work accessible by
++ file transfer protocols such as FTP or HTTP or by shared file
++ systems such as Sun's Network File System (NFS).
++
++ `Compiled Work'
++ A version of the Work that has been processed into a form where it
++ is directly usable on a computer system. This processing may
++ include using installation facilities provided by the Work,
++ transformations of the Work, copying of components of the Work, or
++ other activities. Note that modification of any installation
++ facilities provided by the Work constitutes modification of the Work.
++
++ `Current Maintainer'
++ A person or persons nominated as such within the Work. If there is
++ no such explicit nomination then it is the `Copyright Holder' under
++ any applicable law.
++
++ `Base Interpreter'
++ A program or process that is normally needed for running or
++ interpreting a part or the whole of the Work.
++
++ A Base Interpreter may depend on external components but these
++ are not considered part of the Base Interpreter provided that each
++ external component clearly identifies itself whenever it is used
++ interactively. Unless explicitly specified when applying the
++ license to the Work, the only applicable Base Interpreter is a
++ `LaTeX-Format' or in the case of files belonging to the
++ `LaTeX-format' a program implementing the `TeX language'.
++
++
++
++ CONDITIONS ON DISTRIBUTION AND MODIFICATION
++ ===========================================
++
++ 1. Activities other than distribution and/or modification of the Work
++ are not covered by this license; they are outside its scope. In
++ particular, the act of running the Work is not restricted and no
++ requirements are made concerning any offers of support for the Work.
++
++ 2. You may distribute a complete, unmodified copy of the Work as you
++ received it. Distribution of only part of the Work is considered
++ modification of the Work, and no right to distribute such a Derived
++ Work may be assumed under the terms of this clause.
++
++ 3. You may distribute a Compiled Work that has been generated from a
++ complete, unmodified copy of the Work as distributed under Clause 2
++ above, as long as that Compiled Work is distributed in such a way that
++ the recipients may install the Compiled Work on their system exactly
++ as it would have been installed if they generated a Compiled Work
++ directly from the Work.
++
++ 4. If you are the Current Maintainer of the Work, you may, without
++ restriction, modify the Work, thus creating a Derived Work. You may
++ also distribute the Derived Work without restriction, including
++ Compiled Works generated from the Derived Work. Derived Works
++ distributed in this manner by the Current Maintainer are considered to
++ be updated versions of the Work.
++
++ 5. If you are not the Current Maintainer of the Work, you may modify
++ your copy of the Work, thus creating a Derived Work based on the Work,
++ and compile this Derived Work, thus creating a Compiled Work based on
++ the Derived Work.
++
++ 6. If you are not the Current Maintainer of the Work, you may
++ distribute a Derived Work provided the following conditions are met
++ for every component of the Work unless that component clearly states
++ in the copyright notice that it is exempt from that condition. Only
++ the Current Maintainer is allowed to add such statements of exemption
++ to a component of the Work.
++
++ a. If a component of this Derived Work can be a direct replacement
++ for a component of the Work when that component is used with the
++ Base Interpreter, then, wherever this component of the Work
++ identifies itself to the user when used interactively with that
++ Base Interpreter, the replacement component of this Derived Work
++ clearly and unambiguously identifies itself as a modified version
++ of this component to the user when used interactively with that
++ Base Interpreter.
++
++ b. Every component of the Derived Work contains prominent notices
++ detailing the nature of the changes to that component, or a
++ prominent reference to another file that is distributed as part
++ of the Derived Work and that contains a complete and accurate log
++ of the changes.
++
++ c. No information in the Derived Work implies that any persons,
++ including (but not limited to) the authors of the original version
++ of the Work, provide any support, including (but not limited to)
++ the reporting and handling of errors, to recipients of the
++ Derived Work unless those persons have stated explicitly that
++ they do provide such support for the Derived Work.
++
++ d. You distribute at least one of the following with the Derived Work:
++
++ 1. A complete, unmodified copy of the Work;
++ if your distribution of a modified component is made by
++ offering access to copy the modified component from a
++ designated place, then offering equivalent access to copy
++ the Work from the same or some similar place meets this
++ condition, even though third parties are not compelled to
++ copy the Work along with the modified component;
++
++ 2. Information that is sufficient to obtain a complete,
++ unmodified copy of the Work.
++
++ 7. If you are not the Current Maintainer of the Work, you may
++ distribute a Compiled Work generated from a Derived Work, as long as
++ the Derived Work is distributed to all recipients of the Compiled
++ Work, and as long as the conditions of Clause 6, above, are met with
++ regard to the Derived Work.
++
++ 8. The conditions above are not intended to prohibit, and hence do not
++ apply to, the modification, by any method, of any component so that it
++ becomes identical to an updated version of that component of the Work as
++ it is distributed by the Current Maintainer under Clause 4, above.
++
++ 9. Distribution of the Work or any Derived Work in an alternative
++ format, where the Work or that Derived Work (in whole or in part) is
++ then produced by applying some process to that format, does not relax or
++ nullify any sections of this license as they pertain to the results of
++ applying that process.
++
++ 10. a. A Derived Work may be distributed under a different license
++ provided that license itself honors the conditions listed in
++ Clause 6 above, in regard to the Work, though it does not have
++ to honor the rest of the conditions in this license.
++
++ b. If a Derived Work is distributed under a different license, that
++ Derived Work must provide sufficient documentation as part of
++ itself to allow each recipient of that Derived Work to honor the
++ restrictions in Clause 6 above, concerning changes from the Work.
++
++ 11. This license places no restrictions on works that are unrelated to
++ the Work, nor does this license place any restrictions on aggregating
++ such works with the Work by any means.
++
++ 12. Nothing in this license is intended to, or may be used to, prevent
++ complete compliance by all parties with all applicable laws.
++
++
++ NO WARRANTY
++ ===========
++
++ There is no warranty for the Work. Except when otherwise stated in
++ writing, the Copyright Holder provides the Work `as is', without
++ warranty of any kind, either expressed or implied, including, but not
++ limited to, the implied warranties of merchantability and fitness for a
++ particular purpose. The entire risk as to the quality and performance
++ of the Work is with you. Should the Work prove defective, you assume
++ the cost of all necessary servicing, repair, or correction.
++
++ In no event unless required by applicable law or agreed to in writing
++ will The Copyright Holder, or any author named in the components of the
++ Work, or any other party who may distribute and/or modify the Work as
++ permitted above, be liable to you for damages, including any general,
++ special, incidental or consequential damages arising out of any use of
++ the Work or out of inability to use the Work (including, but not limited
++ to, loss of data, data being rendered inaccurate, or losses sustained by
++ anyone as a result of any failure of the Work to operate with any other
++ programs), even if the Copyright Holder or said author or said other
++ party has been advised of the possibility of such damages.
++
++
++ MAINTENANCE OF THE WORK
++ =======================
++
++ The Work has the status `author-maintained' if the Copyright Holder
++ explicitly and prominently states near the primary copyright notice in
++ the Work that the Work can only be maintained by the Copyright Holder
++ or simply that it is `author-maintained'.
++
++ The Work has the status `maintained' if there is a Current Maintainer
++ who has indicated in the Work that they are willing to receive error
++ reports for the Work (for example, by supplying a valid e-mail
++ address). It is not required for the Current Maintainer to acknowledge
++ or act upon these error reports.
++
++ The Work changes from status `maintained' to `unmaintained' if there
++ is no Current Maintainer, or the person stated to be Current
++ Maintainer of the work cannot be reached through the indicated means
++ of communication for a period of six months, and there are no other
++ significant signs of active maintenance.
++
++ You can become the Current Maintainer of the Work by agreement with
++ any existing Current Maintainer to take over this role.
++
++ If the Work is unmaintained, you can become the Current Maintainer of
++ the Work through the following steps:
++
++ 1. Make a reasonable attempt to trace the Current Maintainer (and
++ the Copyright Holder, if the two differ) through the means of
++ an Internet or similar search.
++
++ 2. If this search is successful, then enquire whether the Work
++ is still maintained.
++
++ a. If it is being maintained, then ask the Current Maintainer
++ to update their communication data within one month.
++
++ b. If the search is unsuccessful or no action to resume active
++ maintenance is taken by the Current Maintainer, then announce
++ within the pertinent community your intention to take over
++ maintenance. (If the Work is a LaTeX work, this could be
++ done, for example, by posting to comp.text.tex.)
++
++ 3a. If the Current Maintainer is reachable and agrees to pass
++ maintenance of the Work to you, then this takes effect
++ immediately upon announcement.
++
++ b. If the Current Maintainer is not reachable and the Copyright
++ Holder agrees that maintenance of the Work be passed to you,
++ then this takes effect immediately upon announcement.
++
++ 4. If you make an `intention announcement' as described in 2b. above
++ and after three months your intention is challenged neither by
++ the Current Maintainer nor by the Copyright Holder nor by other
++ people, then you may arrange for the Work to be changed so as
++ to name you as the (new) Current Maintainer.
++
++ 5. If the previously unreachable Current Maintainer becomes
++ reachable once more within three months of a change completed
++ under the terms of 3b) or 4), then that Current Maintainer must
++ become or remain the Current Maintainer upon request provided
++ they then update their communication data within one month.
++
++ A change in the Current Maintainer does not, of itself, alter the fact
++ that the Work is distributed under the LPPL license.
++
++ If you become the Current Maintainer of the Work, you should
++ immediately provide, within the Work, a prominent and unambiguous
++ statement of your status as Current Maintainer. You should also
++ announce your new status to the same pertinent community as
++ in 2b) above.
++
++
++ WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
++ ======================================================
++
++ This section contains important instructions, examples, and
++ recommendations for authors who are considering distributing their
++ works under this license. These authors are addressed as `you' in
++ this section.
++
++ Choosing This License or Another License
++ ----------------------------------------
++
++ If for any part of your work you want or need to use *distribution*
++ conditions that differ significantly from those in this license, then
++ do not refer to this license anywhere in your work but, instead,
++ distribute your work under a different license. You may use the text
++ of this license as a model for your own license, but your license
++ should not refer to the LPPL or otherwise give the impression that
++ your work is distributed under the LPPL.
++
++ The document `modguide.tex' in the base LaTeX distribution explains
++ the motivation behind the conditions of this license. It explains,
++ for example, why distributing LaTeX under the GNU General Public
++ License (GPL) was considered inappropriate. Even if your work is
++ unrelated to LaTeX, the discussion in `modguide.tex' may still be
++ relevant, and authors intending to distribute their works under any
++ license are encouraged to read it.
++
++ A Recommendation on Modification Without Distribution
++ -----------------------------------------------------
++
++ It is wise never to modify a component of the Work, even for your own
++ personal use, without also meeting the above conditions for
++ distributing the modified component. While you might intend that such
++ modifications will never be distributed, often this will happen by
++ accident -- you may forget that you have modified that component; or
++ it may not occur to you when allowing others to access the modified
++ version that you are thus distributing it and violating the conditions
++ of this license in ways that could have legal implications and, worse,
++ cause problems for the community. It is therefore usually in your
++ best interest to keep your copy of the Work identical with the public
++ one. Many works provide ways to control the behavior of that work
++ without altering any of its licensed components.
++
++ How to Use This License
++ -----------------------
++
++ To use this license, place in each of the components of your work both
++ an explicit copyright notice including your name and the year the work
++ was authored and/or last substantially modified. Include also a
++ statement that the distribution and/or modification of that
++ component is constrained by the conditions in this license.
++
++ Here is an example of such a notice and statement:
++
++ %% pig.dtx
++ %% Copyright 2005 M. Y. Name
++ %
++ % This work may be distributed and/or modified under the
++ % conditions of the LaTeX Project Public License, either version 1.3
++ % of this license or (at your option) any later version.
++ % The latest version of this license is in
++ % http://www.latex-project.org/lppl.txt
++ % and version 1.3 or later is part of all distributions of LaTeX
++ % version 2005/12/01 or later.
++ %
++ % This work has the LPPL maintenance status `maintained'.
++ %
++ % The Current Maintainer of this work is M. Y. Name.
++ %
++ % This work consists of the files pig.dtx and pig.ins
++ % and the derived file pig.sty.
++
++ Given such a notice and statement in a file, the conditions
++ given in this license document would apply, with the `Work' referring
++ to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
++ generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
++ referring to any `LaTeX-Format', and both `Copyright Holder' and
++ `Current Maintainer' referring to the person `M. Y. Name'.
++
++ If you do not want the Maintenance section of LPPL to apply to your
++ Work, change `maintained' above into `author-maintained'.
++ However, we recommend that you use `maintained', as the Maintenance
++ section was added in order to ensure that your Work remains useful to
++ the community even when you can no longer maintain and support it
++ yourself.
++
++ Derived Works That Are Not Replacements
++ ---------------------------------------
++
++ Several clauses of the LPPL specify means to provide reliability and
++ stability for the user community. They therefore concern themselves
++ with the case that a Derived Work is intended to be used as a
++ (compatible or incompatible) replacement of the original Work. If
++ this is not the case (e.g., if a few lines of code are reused for a
++ completely different task), then clauses 6b and 6d shall not apply.
++
++
++ Important Recommendations
++ -------------------------
++
++ Defining What Constitutes the Work
++
++ The LPPL requires that distributions of the Work contain all the
++ files of the Work. It is therefore important that you provide a
++ way for the licensee to determine which files constitute the Work.
++ This could, for example, be achieved by explicitly listing all the
++ files of the Work near the copyright notice of each file or by
++ using a line such as:
++
++ % This work consists of all files listed in manifest.txt.
++
++ in that place. In the absence of an unequivocal list it might be
++ impossible for the licensee to determine what is considered by you
++ to comprise the Work and, in such a case, the licensee would be
++ entitled to make reasonable conjectures as to which files comprise
++ the Work.
++
++Files: debian/*
++
+The Debian packaging is (C) 2008, Tim Abbott <tabbott at mit.edu> and
+is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
diff --combined debian/libtachyon-0.99.install
index 96acadb,0000000..96acadb
mode 100644,000000..100644
--- a/debian/libtachyon-0.99.install
+++ b/debian/libtachyon-0.99.install
@@@ -1,1 -1,0 +1,1 @@@
+compile/*/libtachyon-*.so usr/lib
diff --combined debian/patches/enable-png.patch
index a2057ed,0000000..42bb0e5
mode 100644,000000..100644
--- a/debian/patches/enable-png.patch
+++ b/debian/patches/enable-png.patch
@@@ -1,21 -1,0 +1,21 @@@
+--- tachyon/unix/Make-config 2007-01-24 03:35:44.000000000 -0500
- +++ ../tachyon-0.98~beta/unix/Make-config 2007-05-06 00:55:52.000000000 -0400
+++++ tachyon-0.98~beta/unix/Make-config 2007-05-06 00:55:52.000000000 -0400
+@@ -127,15 +127,9 @@
+ # LibPNG can be downlaoded from:
+ # http://www.libpng.org/
+ ##########################################################################
+-# Uncomment the following lines to disable PNG support
+-USEPNG=
+-PNGINC=
+-PNGLIB=
+-
+-# Uncomment the following lines to enable PNG support
+-#USEPNG= -DUSEPNG
+-#PNGINC= -I/usr/local/include
+-#PNGLIB= -L/usr/local/lib -lpng -lz
++USEPNG= -DUSEPNG
++PNGINC= -I$(SAGE_LOCAL)/include
++PNGLIB= -L$(SAGE_LOCAL)/lib -lpng -lz
+
+
+ ##########################################################################
diff --combined debian/patches/shared-library.patch
index 233c96e,0000000..a2f1092
mode 100644,000000..100644
--- a/debian/patches/shared-library.patch
+++ b/debian/patches/shared-library.patch
@@@ -1,190 -1,0 +1,190 @@@
+Index: src/unix/Makefile
+===================================================================
+--- src.orig/unix/Makefile 2008-05-25 17:58:01.000000000 -0400
++++ src/unix/Makefile 2008-05-25 17:59:05.000000000 -0400
+@@ -23,6 +23,7 @@
+ # Name of raytracing library file to create
+ #
+ RAYLIB=${ARCHDIR}/libtachyon.a
++RAYSHLIB=${ARCHDIR}/libtachyon.so
+ RAYLIBDIR=${ARCHDIR}
+
+ #
+@@ -71,7 +72,7 @@
+ # No test programs included..
+ #
+ BINARIES = ${COMPILEDIR} ${ARCHDIR} ${OBJDIR} ${PARSEDIRS} \
+- ${RAYLIB} ${PARSELIB} ${ARCHDIR}/tachyon
++ ${RAYLIB} ${PARSELIB} ${ARCHDIR}/tachyon ${RAYSHLIB}
+
+
+ #----------------------------------------------------------------------
+@@ -259,119 +260,130 @@
+ ${AR} ${ARFLAGS} ${RAYLIB} ${RAYOBJS}
+ ${RANLIB} ${RAYLIB}
+
++shobj : ${RAYOBJS}
++shobj : FPICFLAG = -fPIC
++
- +${RAYSHLIB} : VERSION=$(shell grep TACHYON_VERSION_STRING ../src/rtcommon.h | cut -d\" -f 2)
+++${RAYSHLIB} : VERSION=$(shell grep TACHYON_VERSION_STRING ../src/tachyon.h | cut -d\" -f 2)
++${RAYSHLIB} : DIRNAME=tachyon-${VERSION}
++${RAYSHLIB} :
++ -rm -f ${RAYOBJS}
++ make shobj
++ ${CC} -fPIC -shared -Wl,-soname,lib${DIRNAME}.so -o ${RAYLIBDIR}/lib${DIRNAME}.so ${CFLAGS} -lpng -lm -lpthread ${RAYOBJS}
++ ln -s lib${DIRNAME}.so $@
++
+ ${OBJDIR}/vol.o : ${SRCDIR}/vol.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/vol.c -o ${OBJDIR}/vol.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/vol.c -o ${OBJDIR}/vol.o
+
+ ${OBJDIR}/extvol.o : ${SRCDIR}/extvol.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/extvol.c -o ${OBJDIR}/extvol.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/extvol.c -o ${OBJDIR}/extvol.o
+
+ ${OBJDIR}/winbmp.o : ${SRCDIR}/winbmp.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/winbmp.c -o ${OBJDIR}/winbmp.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/winbmp.c -o ${OBJDIR}/winbmp.o
+
+ ${OBJDIR}/vector.o : ${SRCDIR}/vector.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/vector.c -o ${OBJDIR}/vector.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/vector.c -o ${OBJDIR}/vector.o
+
+ ${OBJDIR}/triangle.o : ${SRCDIR}/triangle.c ${OBJDEPS} ${SRCDIR}/triangle.h
+- ${CC} ${CFLAGS} -c ${SRCDIR}/triangle.c -o ${OBJDIR}/triangle.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/triangle.c -o ${OBJDIR}/triangle.o
+
+ ${OBJDIR}/trace.o : ${SRCDIR}/trace.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/trace.c -o ${OBJDIR}/trace.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/trace.c -o ${OBJDIR}/trace.o
+
+ ${OBJDIR}/threads.o : ${SRCDIR}/threads.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/threads.c -o ${OBJDIR}/threads.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/threads.c -o ${OBJDIR}/threads.o
+
+ ${OBJDIR}/tgafile.o : ${SRCDIR}/tgafile.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/tgafile.c -o ${OBJDIR}/tgafile.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/tgafile.c -o ${OBJDIR}/tgafile.o
+
+ ${OBJDIR}/util.o : ${SRCDIR}/util.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/util.c -o ${OBJDIR}/util.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/util.c -o ${OBJDIR}/util.o
+
+ ${OBJDIR}/ui.o : ${SRCDIR}/ui.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/ui.c -o ${OBJDIR}/ui.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/ui.c -o ${OBJDIR}/ui.o
+
+ ${OBJDIR}/texture.o : ${SRCDIR}/texture.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/texture.c -o ${OBJDIR}/texture.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/texture.c -o ${OBJDIR}/texture.o
+
+ ${OBJDIR}/sphere.o : ${SRCDIR}/sphere.c ${OBJDEPS} ${SRCDIR}/sphere.h
+- ${CC} ${CFLAGS} -c ${SRCDIR}/sphere.c -o ${OBJDIR}/sphere.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/sphere.c -o ${OBJDIR}/sphere.o
+
+ ${OBJDIR}/sgirgb.o : ${SRCDIR}/sgirgb.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/sgirgb.c -o ${OBJDIR}/sgirgb.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/sgirgb.c -o ${OBJDIR}/sgirgb.o
+
+ ${OBJDIR}/shade.o : ${SRCDIR}/shade.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/shade.c -o ${OBJDIR}/shade.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/shade.c -o ${OBJDIR}/shade.o
+
+ ${OBJDIR}/ring.o : ${SRCDIR}/ring.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/ring.c -o ${OBJDIR}/ring.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/ring.c -o ${OBJDIR}/ring.o
+
+ ${OBJDIR}/render.o : ${SRCDIR}/render.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/render.c -o ${OBJDIR}/render.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/render.c -o ${OBJDIR}/render.o
+
+ ${OBJDIR}/quadric.o : ${SRCDIR}/quadric.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/quadric.c -o ${OBJDIR}/quadric.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/quadric.c -o ${OBJDIR}/quadric.o
+
+ ${OBJDIR}/jpeg.o : ${SRCDIR}/jpeg.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/jpeg.c -o ${OBJDIR}/jpeg.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/jpeg.c -o ${OBJDIR}/jpeg.o
+
+ ${OBJDIR}/pngfile.o : ${SRCDIR}/pngfile.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/pngfile.c -o ${OBJDIR}/pngfile.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/pngfile.c -o ${OBJDIR}/pngfile.o
+
+ ${OBJDIR}/ppm.o : ${SRCDIR}/ppm.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/ppm.c -o ${OBJDIR}/ppm.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/ppm.c -o ${OBJDIR}/ppm.o
+
+ ${OBJDIR}/psd.o : ${SRCDIR}/psd.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/psd.c -o ${OBJDIR}/psd.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/psd.c -o ${OBJDIR}/psd.o
+
+ ${OBJDIR}/plane.o : ${SRCDIR}/plane.c ${OBJDEPS} ${SRCDIR}/plane.h
+- ${CC} ${CFLAGS} -c ${SRCDIR}/plane.c -o ${OBJDIR}/plane.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/plane.c -o ${OBJDIR}/plane.o
+
+ ${OBJDIR}/parallel.o : ${SRCDIR}/parallel.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/parallel.c -o ${OBJDIR}/parallel.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/parallel.c -o ${OBJDIR}/parallel.o
+
+ ${OBJDIR}/objbound.o : ${SRCDIR}/objbound.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/objbound.c -o ${OBJDIR}/objbound.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/objbound.c -o ${OBJDIR}/objbound.o
+
+ ${OBJDIR}/light.o : ${SRCDIR}/light.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/light.c -o ${OBJDIR}/light.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/light.c -o ${OBJDIR}/light.o
+
+ ${OBJDIR}/intersect.o : ${SRCDIR}/intersect.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/intersect.c -o ${OBJDIR}/intersect.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/intersect.c -o ${OBJDIR}/intersect.o
+
+ ${OBJDIR}/imageio.o : ${SRCDIR}/imageio.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/imageio.c -o ${OBJDIR}/imageio.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/imageio.c -o ${OBJDIR}/imageio.o
+
+ ${OBJDIR}/imap.o : ${SRCDIR}/imap.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/imap.c -o ${OBJDIR}/imap.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/imap.c -o ${OBJDIR}/imap.o
+
+ ${OBJDIR}/grid.o : ${SRCDIR}/grid.c ${SRCDIR}/grid.h ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/grid.c -o ${OBJDIR}/grid.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/grid.c -o ${OBJDIR}/grid.o
+
+ ${OBJDIR}/global.o : ${SRCDIR}/global.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/global.c -o ${OBJDIR}/global.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/global.c -o ${OBJDIR}/global.o
+
+ ${OBJDIR}/hash.o : ${SRCDIR}/hash.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/hash.c -o ${OBJDIR}/hash.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/hash.c -o ${OBJDIR}/hash.o
+
+ ${OBJDIR}/cylinder.o : ${SRCDIR}/cylinder.c ${OBJDEPS} ${SRCDIR}/cylinder.h
+- ${CC} ${CFLAGS} -c ${SRCDIR}/cylinder.c -o ${OBJDIR}/cylinder.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/cylinder.c -o ${OBJDIR}/cylinder.o
+
+ ${OBJDIR}/coordsys.o : ${SRCDIR}/coordsys.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/coordsys.c -o ${OBJDIR}/coordsys.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/coordsys.c -o ${OBJDIR}/coordsys.o
+
+ ${OBJDIR}/camera.o : ${SRCDIR}/camera.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/camera.c -o ${OBJDIR}/camera.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/camera.c -o ${OBJDIR}/camera.o
+
+ ${OBJDIR}/box.o : ${SRCDIR}/box.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/box.c -o ${OBJDIR}/box.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/box.c -o ${OBJDIR}/box.o
+
+ ${OBJDIR}/bndbox.o : ${SRCDIR}/bndbox.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/bndbox.c -o ${OBJDIR}/bndbox.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/bndbox.c -o ${OBJDIR}/bndbox.o
+
+ ${OBJDIR}/apigeom.o : ${SRCDIR}/apigeom.c ${OBJDEPS}
+- ${CC} ${CFLAGS} -c ${SRCDIR}/apigeom.c -o ${OBJDIR}/apigeom.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/apigeom.c -o ${OBJDIR}/apigeom.o
+
+ ${OBJDIR}/api.o : ${SRCDIR}/api.c ${OBJDEPS} ${SRCDIR}/sphere.h ${SRCDIR}/plane.h ${SRCDIR}/triangle.h ${SRCDIR}/cylinder.h
+- ${CC} ${CFLAGS} -c ${SRCDIR}/api.c -o ${OBJDIR}/api.o
++ ${CC} ${CFLAGS} ${FPICFLAG} -c ${SRCDIR}/api.c -o ${OBJDIR}/api.o
+
+ clean :
+ @echo "Cleaning object files, binaries etc."
diff --combined debian/rules
index 78fdb48,0000000..827736d
mode 100755,000000..100755
--- a/debian/rules
+++ b/debian/rules
@@@ -1,9 -1,0 +1,11 @@@
+#!/usr/bin/make -f
+
+include /usr/share/cdbs/1/rules/debhelper.mk
+include /usr/share/cdbs/1/class/makefile.mk
- include /usr/share/cdbs/1/rules/patchsys-quilt.mk
+
+DEB_MAKE_INVOKE += -C unix
+
+DEB_MAKE_BUILD_TARGET=linux-base-thr
++
++build-indep:
++ $(MAKE) -C docs pdf
diff --combined debian/source/format
index 0000000,0000000..163aaf8
new file mode 100644
--- /dev/null
+++ b/debian/source/format
@@@ -1,0 -1,0 +1,1 @@@
++3.0 (quilt)
diff --combined debian/tachyon-doc.docs
index 5b94ae8,0000000..5b94ae8
mode 100644,000000..100644
--- a/debian/tachyon-doc.docs
+++ b/debian/tachyon-doc.docs
@@@ -1,1 -1,0 +1,1 @@@
+docs/tachyon.pdf
diff --combined debian/tachyon.docs
index 5b94ae8,0000000..8230d18
mode 100644,000000..100644
--- a/debian/tachyon.docs
+++ b/debian/tachyon.docs
@@@ -1,1 -1,0 +1,2 @@@
- docs/tachyon.pdf
++README
++Changes
diff --combined debian/tachyon.install
index 4c4b7cb,0000000..807d85e
mode 100644,000000..100644
--- a/debian/tachyon.install
+++ b/debian/tachyon.install
@@@ -1,2 -1,0 +1,1 @@@
+compile/*/tachyon usr/bin
- debian/tachyon.1 usr/share/man/man1
diff --combined debian/tachyon.manpages
index 0000000,0000000..263368b
new file mode 100644
--- /dev/null
+++ b/debian/tachyon.manpages
@@@ -1,0 -1,0 +1,1 @@@
++debian/tachyon.1
--
Packaging for tachyon
More information about the debian-science-commits
mailing list