[med-svn] [Git][med-team/sambamba][upstream] New upstream version 0.8.0+dfsg
Nilesh Patra (@nilesh)
gitlab at salsa.debian.org
Tue Jul 20 22:15:44 BST 2021
Nilesh Patra pushed to branch upstream at Debian Med / sambamba
Commits:
83d2a9f4 by Nilesh Patra at 2021-07-20T20:28:32+00:00
New upstream version 0.8.0+dfsg
- - - - -
5 changed files:
- − contrib/shunit2-2.0.3/CHANGES-2.0.txt
- − contrib/shunit2-2.0.3/LGPL-2.1
- − contrib/shunit2-2.0.3/README.txt
- − contrib/shunit2-2.0.3/contributors.txt
- − contrib/shunit2-2.0.3/shunit2
Changes:
=====================================
contrib/shunit2-2.0.3/CHANGES-2.0.txt deleted
=====================================
@@ -1,68 +0,0 @@
-CHANGES WITH 2.0.4
-
-Unset additional variables that were missed.
-
-Fixed off-by-one in exit value for scripts caught by the trap handler.
-
-The library did not fail gracefully when the 'od' command was not installed.
-
-
-CHANGES WITH 2.0.3
-
-Back ported the Makefile from 2.1.1pre that included changes to the
-docs-docbook-prep target.
-
-Changed the test in assertFalse() so that any non-zero value registers as
-false. (Credits to Bryan Larsen)
-
-Updated the testPartyLikeItIs1999() function in the Quick Start documentation.
-The 'expected' and 'actual' values were swapped. (Credits to Richard Jensen)
-
-It was pointed out that the simple 'failed' message for a failed assert was not
-only insufficient, it was nonstandard (when compared to JUnit) and didn't
-provide the user with an expected vs actual result. The code was revised
-somewhat to bring closer into alignment with JUnit (v4.3.1 specifically) so
-that it feels more "normal". (Credits to Richard Jensen)
-
-As part of the JUnit realignment, it was noticed that fail*() functions in
-JUnit don't actually do any comparisons themselves. They only generate a
-failure message. Updated the code to match.
-
-Added self-testing unit tests. Kinda horkey, but they did find bugs during the
-JUnit realignment.
-
-Fixed the code for returning from asserts as the return was being called before
-the unsetting of variables occurred. (Credits to Mathias Goldau)
-
-The assert(True|False)() functions now accept an integer value for a
-conditional test. A value of '0' is considered 'true', while any non-zero value
-is considered 'false'.
-
-All public functions now fill use default values to work properly with the '-x'
-shell debugging flag.
-
-Fixed the method of percent calculation for the report to get achieve better
-accuracy.
-
-
-CHANGES WITH 2.0.2
-
-Fixed problem with fail(). The failure message was not properly printed.
-
-Reworked the Makefile so that the DocBook XML and XSLT files are properly
-downloaded before parsing can continue.
-
-
-CHANGES WITH 2.0.1
-
-Fixed some really stupid mistakes with the fail* functions. They were doing the
-exact opposite of what they were supposed to be doing.
-
-
-CHANGES WITH 2.0.0
-
-Made the first stand-alone release!
-
-
-$Revision$
-vim:spell
=====================================
contrib/shunit2-2.0.3/LGPL-2.1 deleted
=====================================
@@ -1,504 +0,0 @@
- GNU LESSER GENERAL PUBLIC LICENSE
- Version 2.1, February 1999
-
- Copyright (C) 1991, 1999 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
- as the successor of the GNU Library Public License, version 2, hence
- the version number 2.1.]
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-Licenses are intended to guarantee your freedom to share and change
-free software--to make sure the software is free for all its users.
-
- This license, the Lesser General Public License, applies to some
-specially designated software packages--typically libraries--of the
-Free Software Foundation and other authors who decide to use it. You
-can use it too, but we suggest you first think carefully about whether
-this license or the ordinary General Public License is the better
-strategy to use in any particular case, based on the explanations below.
-
- When we speak of free software, we are referring to freedom of use,
-not price. Our General Public Licenses are designed to make sure that
-you have the freedom to distribute copies of free software (and charge
-for this service if you wish); that you receive source code or can get
-it if you want it; that you can change the software and use pieces of
-it in new free programs; and that you are informed that you can do
-these things.
-
- To protect your rights, we need to make restrictions that forbid
-distributors to deny you these rights or to ask you to surrender these
-rights. These restrictions translate to certain responsibilities for
-you if you distribute copies of the library or if you modify it.
-
- For example, if you distribute copies of the library, whether gratis
-or for a fee, you must give the recipients all the rights that we gave
-you. You must make sure that they, too, receive or can get the source
-code. If you link other code with the library, you must provide
-complete object files to the recipients, so that they can relink them
-with the library after making changes to the library and recompiling
-it. And you must show them these terms so they know their rights.
-
- We protect your rights with a two-step method: (1) we copyright the
-library, and (2) we offer you this license, which gives you legal
-permission to copy, distribute and/or modify the library.
-
- To protect each distributor, we want to make it very clear that
-there is no warranty for the free library. Also, if the library is
-modified by someone else and passed on, the recipients should know
-that what they have is not the original version, so that the original
-author's reputation will not be affected by problems that might be
-introduced by others.
-
- Finally, software patents pose a constant threat to the existence of
-any free program. We wish to make sure that a company cannot
-effectively restrict the users of a free program by obtaining a
-restrictive license from a patent holder. Therefore, we insist that
-any patent license obtained for a version of the library must be
-consistent with the full freedom of use specified in this license.
-
- Most GNU software, including some libraries, is covered by the
-ordinary GNU General Public License. This license, the GNU Lesser
-General Public License, applies to certain designated libraries, and
-is quite different from the ordinary General Public License. We use
-this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
- When a program is linked with a library, whether statically or using
-a shared library, the combination of the two is legally speaking a
-combined work, a derivative of the original library. The ordinary
-General Public License therefore permits such linking only if the
-entire combination fits its criteria of freedom. The Lesser General
-Public License permits more lax criteria for linking other code with
-the library.
-
- We call this license the "Lesser" General Public License because it
-does Less to protect the user's freedom than the ordinary General
-Public License. It also provides other free software developers Less
-of an advantage over competing non-free programs. These disadvantages
-are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain
-special circumstances.
-
- For example, on rare occasions, there may be a special need to
-encourage the widest possible use of a certain library, so that it becomes
-a de-facto standard. To achieve this, non-free programs must be
-allowed to use the library. A more frequent case is that a free
-library does the same job as widely used non-free libraries. In this
-case, there is little to gain by limiting the free library to free
-software only, so we use the Lesser General Public License.
-
- In other cases, permission to use a particular library in non-free
-programs enables a greater number of people to use a large body of
-free software. For example, permission to use the GNU C Library in
-non-free programs enables many more people to use the whole GNU
-operating system, as well as its variant, the GNU/Linux operating
-system.
-
- Although the Lesser General Public License is Less protective of the
-users' freedom, it does ensure that the user of a program that is
-linked with the Library has the freedom and the wherewithal to run
-that program using a modified version of the Library.
-
- The precise terms and conditions for copying, distribution and
-modification follow. Pay close attention to the difference between a
-"work based on the library" and a "work that uses the library". The
-former contains code derived from the library, whereas the latter must
-be combined with the library in order to run.
-
- GNU LESSER GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License Agreement applies to any software library or other
-program which contains a notice placed by the copyright holder or
-other authorized party saying it may be distributed under the terms of
-this Lesser General Public License (also called "this License").
-Each licensee is addressed as "you".
-
- A "library" means a collection of software functions and/or data
-prepared so as to be conveniently linked with application programs
-(which use some of those functions and data) to form executables.
-
- The "Library", below, refers to any such software library or work
-which has been distributed under these terms. A "work based on the
-Library" means either the Library or any derivative work under
-copyright law: that is to say, a work containing the Library or a
-portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is
-included without limitation in the term "modification".)
-
- "Source code" for a work means the preferred form of the work for
-making modifications to it. For a library, complete source code means
-all the source code for all modules it contains, plus any associated
-interface definition files, plus the scripts used to control compilation
-and installation of the library.
-
- Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running a program using the Library is not restricted, and output from
-such a program is covered only if its contents constitute a work based
-on the Library (independent of the use of the Library in a tool for
-writing it). Whether that is true depends on what the Library does
-and what the program that uses the Library does.
-
- 1. You may copy and distribute verbatim copies of the Library's
-complete source code as you receive it, in any medium, provided that
-you conspicuously and appropriately publish on each copy an
-appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any
-warranty; and distribute a copy of this License along with the
-Library.
-
- You may charge a fee for the physical act of transferring a copy,
-and you may at your option offer warranty protection in exchange for a
-fee.
-
- 2. You may modify your copy or copies of the Library or any portion
-of it, thus forming a work based on the Library, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) The modified work must itself be a software library.
-
- b) You must cause the files modified to carry prominent notices
- stating that you changed the files and the date of any change.
-
- c) You must cause the whole of the work to be licensed at no
- charge to all third parties under the terms of this License.
-
- d) If a facility in the modified Library refers to a function or a
- table of data to be supplied by an application program that uses
- the facility, other than as an argument passed when the facility
- is invoked, then you must make a good faith effort to ensure that,
- in the event an application does not supply such function or
- table, the facility still operates, and performs whatever part of
- its purpose remains meaningful.
-
- (For example, a function in a library to compute square roots has
- a purpose that is entirely well-defined independent of the
- application. Therefore, Subsection 2d requires that any
- application-supplied function or table used by this function must
- be optional: if the application does not supply it, the square
- root function must still compute square roots.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Library,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Library, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library
-with the Library (or with a work based on the Library) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may opt to apply the terms of the ordinary GNU General Public
-License instead of this License to a given copy of the Library. To do
-this, you must alter all the notices that refer to this License, so
-that they refer to the ordinary GNU General Public License, version 2,
-instead of to this License. (If a newer version than version 2 of the
-ordinary GNU General Public License has appeared, then you can specify
-that version instead if you wish.) Do not make any other change in
-these notices.
-
- Once this change is made in a given copy, it is irreversible for
-that copy, so the ordinary GNU General Public License applies to all
-subsequent copies and derivative works made from that copy.
-
- This option is useful when you wish to copy part of the code of
-the Library into a program that is not a library.
-
- 4. You may copy and distribute the Library (or a portion or
-derivative of it, under Section 2) in object code or executable form
-under the terms of Sections 1 and 2 above provided that you accompany
-it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a
-medium customarily used for software interchange.
-
- If distribution of object code is made by offering access to copy
-from a designated place, then offering equivalent access to copy the
-source code from the same place satisfies the requirement to
-distribute the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 5. A program that contains no derivative of any portion of the
-Library, but is designed to work with the Library by being compiled or
-linked with it, is called a "work that uses the Library". Such a
-work, in isolation, is not a derivative work of the Library, and
-therefore falls outside the scope of this License.
-
- However, linking a "work that uses the Library" with the Library
-creates an executable that is a derivative of the Library (because it
-contains portions of the Library), rather than a "work that uses the
-library". The executable is therefore covered by this License.
-Section 6 states terms for distribution of such executables.
-
- When a "work that uses the Library" uses material from a header file
-that is part of the Library, the object code for the work may be a
-derivative work of the Library even though the source code is not.
-Whether this is true is especially significant if the work can be
-linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
- If such an object file uses only numerical parameters, data
-structure layouts and accessors, and small macros and small inline
-functions (ten lines or less in length), then the use of the object
-file is unrestricted, regardless of whether it is legally a derivative
-work. (Executables containing this object code plus portions of the
-Library will still fall under Section 6.)
-
- Otherwise, if the work is a derivative of the Library, you may
-distribute the object code for the work under the terms of Section 6.
-Any executables containing that work also fall under Section 6,
-whether or not they are linked directly with the Library itself.
-
- 6. As an exception to the Sections above, you may also combine or
-link a "work that uses the Library" with the Library to produce a
-work containing portions of the Library, and distribute that work
-under terms of your choice, provided that the terms permit
-modification of the work for the customer's own use and reverse
-engineering for debugging such modifications.
-
- You must give prominent notice with each copy of the work that the
-Library is used in it and that the Library and its use are covered by
-this License. You must supply a copy of this License. If the work
-during execution displays copyright notices, you must include the
-copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one
-of these things:
-
- a) Accompany the work with the complete corresponding
- machine-readable source code for the Library including whatever
- changes were used in the work (which must be distributed under
- Sections 1 and 2 above); and, if the work is an executable linked
- with the Library, with the complete machine-readable "work that
- uses the Library", as object code and/or source code, so that the
- user can modify the Library and then relink to produce a modified
- executable containing the modified Library. (It is understood
- that the user who changes the contents of definitions files in the
- Library will not necessarily be able to recompile the application
- to use the modified definitions.)
-
- b) Use a suitable shared library mechanism for linking with the
- Library. A suitable mechanism is one that (1) uses at run time a
- copy of the library already present on the user's computer system,
- rather than copying library functions into the executable, and (2)
- will operate properly with a modified version of the library, if
- the user installs one, as long as the modified version is
- interface-compatible with the version that the work was made with.
-
- c) Accompany the work with a written offer, valid for at
- least three years, to give the same user the materials
- specified in Subsection 6a, above, for a charge no more
- than the cost of performing this distribution.
-
- d) If distribution of the work is made by offering access to copy
- from a designated place, offer equivalent access to copy the above
- specified materials from the same place.
-
- e) Verify that the user has already received a copy of these
- materials or that you have already sent this user a copy.
-
- For an executable, the required form of the "work that uses the
-Library" must include any data and utility programs needed for
-reproducing the executable from it. However, as a special exception,
-the materials to be distributed need not include anything that is
-normally distributed (in either source or binary form) with the major
-components (compiler, kernel, and so on) of the operating system on
-which the executable runs, unless that component itself accompanies
-the executable.
-
- It may happen that this requirement contradicts the license
-restrictions of other proprietary libraries that do not normally
-accompany the operating system. Such a contradiction means you cannot
-use both them and the Library together in an executable that you
-distribute.
-
- 7. You may place library facilities that are a work based on the
-Library side-by-side in a single library together with other library
-facilities not covered by this License, and distribute such a combined
-library, provided that the separate distribution of the work based on
-the Library and of the other library facilities is otherwise
-permitted, and provided that you do these two things:
-
- a) Accompany the combined library with a copy of the same work
- based on the Library, uncombined with any other library
- facilities. This must be distributed under the terms of the
- Sections above.
-
- b) Give prominent notice with the combined library of the fact
- that part of it is a work based on the Library, and explaining
- where to find the accompanying uncombined form of the same work.
-
- 8. You may not copy, modify, sublicense, link with, or distribute
-the Library except as expressly provided under this License. Any
-attempt otherwise to copy, modify, sublicense, link with, or
-distribute the Library is void, and will automatically terminate your
-rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses
-terminated so long as such parties remain in full compliance.
-
- 9. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Library or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Library or works based on it.
-
- 10. Each time you redistribute the Library (or any work based on the
-Library), the recipient automatically receives a license from the
-original licensor to copy, distribute, link with or modify the Library
-subject to these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties with
-this License.
-
- 11. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Library at all. For example, if a patent
-license would not permit royalty-free redistribution of the Library by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any
-particular circumstance, the balance of the section is intended to apply,
-and the section as a whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 12. If the distribution and/or use of the Library is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Library under this License may add
-an explicit geographical distribution limitation excluding those countries,
-so that distribution is permitted only in or among countries not thus
-excluded. In such case, this License incorporates the limitation as if
-written in the body of this License.
-
- 13. The Free Software Foundation may publish revised and/or new
-versions of the Lesser General Public License from time to time.
-Such new versions will be similar in spirit to the present version,
-but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library
-specifies a version number of this License which applies to it and
-"any later version", you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation. If the Library does not specify a
-license version number, you may choose any version ever published by
-the Free Software Foundation.
-
- 14. If you wish to incorporate parts of the Library into other free
-programs whose distribution conditions are incompatible with these,
-write to the author to ask for permission. For software which is
-copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our
-decision will be guided by the two goals of preserving the free status
-of all derivatives of our free software and of promoting the sharing
-and reuse of software generally.
-
- NO WARRANTY
-
- 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE LIBRARY "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
-LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- How to Apply These Terms to Your New Libraries
-
- If you develop a new library, and you want it to be of the greatest
-possible use to the public, we recommend making it free software that
-everyone can redistribute and change. You can do so by permitting
-redistribution under these terms (or, alternatively, under the terms of the
-ordinary General Public License).
-
- To apply these terms, attach the following notices to the library. It is
-safest to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
- <one line to give the library's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This library 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.1 of the License, or (at your option) any later version.
-
- This library 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 library; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the library, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the
- library `Frob' (a library for tweaking knobs) written by James Random Hacker.
-
- <signature of Ty Coon>, 1 April 1990
- Ty Coon, President of Vice
-
-That's all there is to it!
-
-
=====================================
contrib/shunit2-2.0.3/README.txt deleted
=====================================
@@ -1,153 +0,0 @@
-#------------------------------------------------------------------------------
-# SourceForge
-#
-
-This project is stored on SourceForge as http://sf.net/projects/shunit2. The
-source code can be accessed using the following information.
-
-* Subversion
-$ svn co https://shunit2.svn.sourceforge.net/svnroot/shunit2/trunk/source shunit2
-
-Subversion may also be browsed via a web browser at
-http://svn.sourceforge.net/shunit2
-
-#------------------------------------------------------------------------------
-# Making a release
-#
-
-For these steps, it is assumed we are working with release 2.0.0.
-
-Steps:
-* write release notes
-* update version
-* finish changelog
-* check all the code in
-* tag the release
-* export the release
-* create tarball
-* md5sum the tarball and sign with gpg
-* update website
-* post to SourceForge and Freshmeat
-
-WRITE RELEASE NOTES
-
-This should be pretty self explainatory. Use one of the release notes from a
-previous release as an example.
-
-To get the versions of the various shells, do the following:
-Cygwin
- bash: $ bash --version
- ksh: actually pdksh
- pdksh: look in the downloaded Cygwin directory
-Linux
- bash: $ bash --version
- dash: look at installed version
- ksh: $ ksh --version
- pdksh: $ strings /bin/pdksh |grep 'PD KSH'
- zsh: $ zsh --version
-Solaris 10
- sh: not possible
- bash: $ bash --version
- ksh: $ strings /usr/bin/ksh |grep 'Version'
-
-UPDATE VERSION
-
-Edit the shunit2 source code, and change the version number in the comment, as
-well as in the __SHUNIT_VERSION variable. Next, edit the
-src/docbook/shunit2.xml file, edit the version in the <title> element, and make
-sure there is a revision section for this release.
-
-FINISH DOCUMENTATION
-
-Make sure that any remaning changes get put into the CHANGES-X.X.txt file.
-
-Finish writing the RELEASE_NOTES-X.X.X.txt. Once it is finished, run it through
-the 'fmt' command to make it pretty.
-
-$ fmt -w 80 RELEASE_NOTES-2.0.0.txt >RELEASE_NOTES-2.0.0.txt.new
-$ mv RELEASE_NOTES-2.0.0.txt.new RELEASE_NOTES-2.0.0.txt
-
-We want to have an up-to-date version of the documentation in the release, so
-we'd better build it.
-
-$ pwd
-.../shunit2/source/2.0
-$ make docs
-...
-$ cp -p build/shunit2.html doc
-$ svn ci -m "" doc/shunit2.html
-
-CHECK IN ALL THE CODE
-
-This step is pretty self-explainatory
-
-TAG THE RELEASE
-
-$ pwd
-.../shunit2/source
-$ ls
-2.0 2.1
-$ svn cp -m "Release 2.0.0" \
-2.0 https://shunit2.svn.sourceforge.net/svnroot/shunit2/tags/source/2.0.0
-
-EXPORT THE RELEASE
-
-$ pwd
-.../shunit2/builds
-$ svn export \
-https://shunit2.svn.sourceforge.net/svnroot/shunit2/tags/source/2.0.0 \
-shunit2-2.0.0
-
-CREATE TARBALL
-
-$ tar cfz ../releases/shunit2-2.0.0.tgz shunit2-2.0.0
-
-MD5SUM THE TARBALL AND SIGN WITH GPG
-
-$ cd ../releases
-$ md5sum shunit2-2.0.0.tgz >shunit2-2.0.0.tgz.md5
-$ gpg --default-key kate.ward at forestent.com --detach-sign shunit2-2.0.0.tgz
-
-UPDATE WEBSITE
-
-Again, pretty self-explainatory. Make sure to copy the MD5 and GPG signature
-files. Once that is done, make sure to tag the website so we can go back in
-time if needed.
-
-$ pwd
-.../shunit2
-$ ls
-source website
-$ svn cp -m "Release 2.0.0" \
-website https://shunit2.svn.sourceforge.net/svnroot/shunit2/tags/website/20060916
-
-Now, update the website. It too is held in Subversion, so ssh into SourceForge
-and use 'svn up' to grab the latest version.
-
-POST TO SOURCEFORGE AND FRESHMEAT
-
-http://sourceforge.net/projects/shunit2/
-http://freshmeat.net/
-
-#------------------------------------------------------------------------------
-# Related documentation
-#
-
-Docbook XML
- docbook-xml-4.4.zip
- http://www.docbook.org/xml/4.4/docbook-xml-4.4.zip
- http://www.oasis-open.org/docbook/xml/4.4/docbook-xml-4.4.zip
- docbook-xml-4.5.zip
- http://www.docbook.org/xml/4.5/docbook-xml-4.5.zip
-
-Docbook XSL
- docbook-xsl-1.71.0.tar.bz2
- http://prdownloads.sourceforge.net/docbook/docbook-xsl-1.71.0.tar.bz2?download
- docbook-xsl-1.71.1.tar.bz2
- http://downloads.sourceforge.net/docbook/docbook-xsl-1.71.1.tar.bz2?use_mirror=puzzle
-
-JUnit
- http://www.junit.org
-
-
-$Revision$
=====================================
contrib/shunit2-2.0.3/contributors.txt deleted
=====================================
@@ -1,10 +0,0 @@
-The original author of shunit2 is Kate Ward. The following people have
-contributed in some way or another to shunit2.
-
-Bryan Larsen
-Kevin Van Horn
-Mathias Goldau
-Richard Jensen
-Rob Holland
-
-$Revision$
=====================================
contrib/shunit2-2.0.3/shunit2 deleted
=====================================
@@ -1,799 +0,0 @@
-# $Id$
-# vim:syntax=sh:sts=2
-# vim:foldmethod=marker:foldmarker=/**,*/
-#
-#/**
-# <?xml version="1.0" encoding="UTF-8"?>
-# <s:shelldoc xmlns:s="http://www.forestent.com/projects/shelldoc/xsl/2005.0">
-# <s:header>
-# shUnit 2.0.4
-# Shell Unit Test Framework
-#
-# http://code.google.com/p/shunit2/
-#
-# written by Kate Ward <kate.ward at forestent.com>
-# released under the LGPL
-#
-# this module implements a xUnit based unit test framework similar to JUnit
-# </s:header>
-#*/
-
-# shell flags for shunit:
-# u - treat unset variables as an error when performing parameter expansion
-__SHUNIT_SHELL_FLAGS='u'
-
-# save the current set of shell flags, and then set some for ourselves
-__shunit_oldShellFlags="$-"
-for _shunit_shellFlag in `echo "${__SHUNIT_SHELL_FLAGS}" |sed 's/\(.\)/\1 /g'`
-do
- set -${_shunit_shellFlag}
-done
-unset _shunit_shellFlag
-
-# constants
-
-__SHUNIT_VERSION='2.0.4pre'
-
-__SHUNIT_TRUE=0
-__SHUNIT_FALSE=1
-__SHUNIT_ERROR=2
-
-__SHUNIT_ASSERT_MSG_PREFIX='ASSERT:'
-
-for _su_const in `set |grep "^__SHUNIT_" |cut -d= -f1`; do
- readonly ${_su_const}
-done
-unset _su_const
-
-# variables
-__shunit_suite=''
-
-__shunit_testsPassed=0
-__shunit_testsFailed=0
-__shunit_testsTotal=0
-
-#-----------------------------------------------------------------------------
-# assert functions
-#
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertEquals</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>expected</parameter></paramdef>
-# <paramdef>string <parameter>actual</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Asserts that <emphasis>expected</emphasis> and
-# <emphasis>actual</emphasis> are equal to one another. The message is
-# optional.</para>
-# </entry>
-# </s:function>
-#*/
-assertEquals()
-{
- _su_message=''
- if [ $# -eq 3 ]; then
- _su_message=$1
- shift
- fi
- _su_expected=${1:-}
- _su_actual=${2:-}
-
- shunit_return=${__SHUNIT_TRUE}
- if [ "${_su_expected}" = "${_su_actual}" ]; then
- _shunit_testPassed
- else
- failNotEquals "${_su_message}" "${_su_expected}" "${_su_actual}"
- shunit_return=${__SHUNIT_FALSE}
- fi
-
- unset _su_message _su_expected _su_actual
- return ${shunit_return}
-}
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertNull</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>value</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Asserts that <emphasis>value</emphasis> is <literal>null</literal>,
-# or in shell terms a zero-length string. The message is optional.</para>
-# </entry>
-# </s:function>
-#*/
-assertNull()
-{
- if [ $# -eq 2 ]; then
- assertTrue "$1" "[ -z '$2' ]"
- else
- assertTrue "[ -z '${1:-}' ]"
- fi
-}
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertNotNull</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>value</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Asserts that <emphasis>value</emphasis> is <emphasis
-# role="strong">not</emphasis> <literal>null</literal>, or in shell terms not
-# a zero-length string. The message is optional.</para>
-# </entry>
-# </s:function>
-#*/
-assertNotNull()
-{
- if [ $# -eq 2 ]; then
- assertTrue "$1" "[ -n '$2' ]"
- else
- assertTrue "[ -n '${1:-}' ]"
- fi
-}
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertSame</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>expected</parameter></paramdef>
-# <paramdef>string <parameter>actual</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function is functionally equivalent to
-# <function>assertEquals</function>.</para>
-# </entry>
-# </s:function>
-#*/
-assertSame()
-{
- assertEquals "${@:-}"
-}
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertNotSame</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>unexpected</parameter></paramdef>
-# <paramdef>string <parameter>actual</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Asserts that <emphasis>unexpected</emphasis> and
-# <emphasis>actual</emphasis> are <emphasis role="strong">not</emphasis>
-# equal to one another. The message is optional.</para>
-# </entry>
-# </s:function>
-#*/
-assertNotSame()
-{
- _su_message=''
- if [ $# -eq 3 ]; then
- _su_message=$1
- shift
- fi
- _su_unexpected=${1:-}
- _su_actual=${2:-}
-
- shunit_return=${__SHUNIT_TRUE}
- if [ "${_su_unexpected}" != "${_su_actual}" ]; then
- _shunit_testPassed
- else
- failSame "${_su_message}"
- shunit_return=${__SHUNIT_FALSE}
- fi
-
- unset _su_message _su_unexpected _su_actual
- return ${shunit_return}
-}
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertTrue</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>condition</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Asserts that a given shell test condition is true. The message is
-# optional.</para>
-# <para>Testing whether something is true or false is easy enough by using
-# the assertEquals/assertNotSame functions. Shell supports much more
-# complicated tests though, and a means to support them was needed. As such,
-# this function tests that conditions are true or false through evaluation
-# rather than just looking for a true or false.</para>
-# <funcsynopsis>
-# The following test will succeed: <funcsynopsisinfo>assertTrue "[ 34 -gt 23 ]"</funcsynopsisinfo>
-# The following test will fail with a message: <funcsynopsisinfo>assertTrue "test failed" "[ -r '/non/existent/file' ]"</funcsynopsisinfo>
-# </funcsynopsis>
-# </entry>
-# </s:function>
-#*/
-assertTrue()
-{
- _su_message=''
- if [ $# -eq 2 ]; then
- _su_message=$1
- shift
- fi
- _su_condition=${1:-}
-
- shunit_return=${__SHUNIT_TRUE}
-
- # see if condition is an integer, i.e. a return value
- _su_match=`expr "${_su_condition}" : '\([0-9]*\)'`
- if [ -z "${_su_condition}" ]; then
- # null condition
- shunit_return=${__SHUNIT_FALSE}
- elif [ "${_su_condition}" = "${_su_match}" ]; then
- # possible return value. treating 0 as true, and non-zero as false.
- [ ${_su_condition} -ne 0 ] && shunit_return=${__SHUNIT_FALSE}
- else
- # (hopefully) a condition
- ( eval ${_su_condition} ) >/dev/null 2>&1
- [ $? -ne 0 ] && shunit_return=${__SHUNIT_FALSE}
- fi
-
- # record the test
- if [ ${shunit_return} -eq ${__SHUNIT_TRUE} ]; then
- _shunit_testPassed
- else
- _shunit_testFailed "${_su_message}"
- fi
-
- unset _su_message _su_condition _su_match
- return ${shunit_return}
-}
-
-#/**
-# <s:function group="asserts">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>assertFalse</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>condition</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Asserts that a given shell test condition is false. The message is
-# optional.</para>
-# <para>Testing whether something is true or false is easy enough by using
-# the assertEquals/assertNotSame functions. Shell supports much more
-# complicated tests though, and a means to support them was needed. As such,
-# this function tests that conditions are true or false through evaluation
-# rather than just looking for a true or false.</para>
-# <funcsynopsis>
-# The following test will succeed: <funcsynopsisinfo>assertFalse "[ 'apples' = 'oranges' ]"</funcsynopsisinfo>
-# The following test will fail with a message: <funcsynopsisinfo>assertFalse "test failed" "[ 1 -eq 1 -a 2 -eq 2 ]"</funcsynopsisinfo>
-# </funcsynopsis>
-# </entry>
-# </s:function>
-#*/
-assertFalse()
-{
- _su_message=''
- if [ $# -eq 2 ]; then
- _su_message=$1
- shift
- fi
- _su_condition=${1:-}
-
- shunit_return=${__SHUNIT_TRUE}
-
- # see if condition is an integer, i.e. a return value
- _su_match=`expr "${_su_condition}" : '\([0-9]*\)'`
- if [ -z "${_su_condition}" ]; then
- # null condition
- shunit_return=${__SHUNIT_FALSE}
- elif [ "${_su_condition}" = "${_su_match}" ]; then
- # possible return value. treating 0 as true, and non-zero as false.
- [ ${_su_condition} -eq 0 ] && shunit_return=${__SHUNIT_FALSE}
- else
- # (hopefully) a condition
- ( eval ${_su_condition} ) >/dev/null 2>&1
- [ $? -eq 0 ] && shunit_return=${__SHUNIT_FALSE}
- fi
-
- # record the test
- if [ ${shunit_return} -eq ${__SHUNIT_TRUE} ]; then
- _shunit_testPassed
- else
- _shunit_testFailed "${_su_message}"
- fi
-
- unset _su_message _su_condition _su_match
- return ${shunit_return}
-}
-
-#-----------------------------------------------------------------------------
-# failure functions
-#
-
-#/**
-# <s:function group="failures">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>fail</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Fails the test immediately, with the optional message.</para>
-# </entry>
-# </s:function>
-#*/
-fail()
-{
- _su_message=${1:-}
-
- _shunit_testFailed "${_su_message}"
-
- unset _su_message
-}
-
-#/**
-# <s:function group="failures">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>failNotEquals</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>unexpected</parameter></paramdef>
-# <paramdef>string <parameter>actual</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Fails the test if <emphasis>unexpected</emphasis> and
-# <emphasis>actual</emphasis> are <emphasis role="strong">not</emphasis>
-# equal to one another. The message is optional.</para>
-# </entry>
-# </s:function>
-#*/
-failNotEquals()
-{
- _su_message=''
- if [ $# -eq 3 ]; then
- _su_message=$1
- shift
- fi
- _su_unexpected=${1:-}
- _su_actual=${2:-}
-
- _shunit_testFailed "${_su_message:+${_su_message} }expected:<${_su_unexpected}> but was:<${_su_actual}>"
-
- unset _su_message _su_unexpected _su_actual
-}
-
-#/**
-# <s:function group="failures">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>failSame</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Indicate test failure because arguments were not the same. The
-# message is optional.</para>
-# </entry>
-# </s:function>
-#*/
-failSame()
-{
- _su_message=${1:-}
-
- _shunit_testFailed "${_su_message:+${_su_message} }expected not same"
-
- unset _su_message
-}
-
-#/**
-# <s:function group="failures">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>failNotSame</function></funcdef>
-# <paramdef>string <parameter>[message]</parameter></paramdef>
-# <paramdef>string <parameter>expected</parameter></paramdef>
-# <paramdef>string <parameter>actual</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>Fails the test if <emphasis>expected</emphasis> and
-# <emphasis>actual</emphasis> are equal to one another. The message is
-# optional.</para>
-# </entry>
-# </s:function>
-#*/
-failNotSame()
-{
- failNotEquals "${@:-}"
-}
-
-#-----------------------------------------------------------------------------
-# suite functions
-#
-
-#/**
-# <s:function group="suites">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>suite</function></funcdef>
-# <paramdef />
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function can be optionally overridden by the user in their test
-# suite.</para>
-# <para>If this function exists, it will be called when
-# <command>shunit2</command> is sourced. If it does not exist, shUnit2 will
-# search the parent script for all functions beginning with the word
-# <literal>test</literal>, and they will be added dynamically to the test
-# suite.</para>
-# </entry>
-# </s:function>
-#*/
-# Note: see _shunit_mktempFunc() for actual implementation
-# suite() { :; }
-
-#/**
-# <s:function group="suites">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>suite_addTest</function></funcdef>
-# <paramdef>string <parameter>function</parameter></paramdef>
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function adds a function name to the list of tests scheduled for
-# execution as part of this test suite. This function should only be called
-# from within the <function>suite()</function> function.</para>
-# </entry>
-# </s:function>
-#*/
-suite_addTest()
-{
- _su_func=${1:-}
-
- __shunit_suite="${__shunit_suite:+${__shunit_suite} }${_su_func}"
-
- unset _su_func
-}
-
-#/**
-# <s:function group="suites">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>oneTimeSetUp</function></funcdef>
-# <paramdef />
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function can be be optionally overridden by the user in their
-# test suite.</para>
-# <para>If this function exists, it will be called once before any tests are
-# run. It is useful to prepare a common environment for all tests.</para>
-# </entry>
-# </s:function>
-#*/
-# Note: see _shunit_mktempFunc() for actual implementation
-# oneTimeSetUp() { :; }
-
-#/**
-# <s:function group="suites">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>oneTimeTearDown</function></funcdef>
-# <paramdef />
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function can be be optionally overridden by the user in their
-# test suite.</para>
-# <para>If this function exists, it will be called once after all tests are
-# completed. It is useful to clean up the environment after all tests.</para>
-# </entry>
-# </s:function>
-#*/
-# Note: see _shunit_mktempFunc() for actual implementation
-# oneTimeTearDown() { :; }
-
-#/**
-# <s:function group="suites">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>setUp</function></funcdef>
-# <paramdef />
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function can be be optionally overridden by the user in their
-# test suite.</para>
-# <para>If this function exists, it will be called before each test is run.
-# It is useful to reset the environment before each test.</para>
-# </entry>
-# </s:function>
-#*/
-# Note: see _shunit_mktempFunc() for actual implementation
-# setUp() { :; }
-
-#/**
-# <s:function group="suites">
-# <entry align="right">
-# <emphasis>void</emphasis>
-# </entry>
-# <entry>
-# <funcsynopsis>
-# <funcprototype>
-# <funcdef><function>tearDown</function></funcdef>
-# <paramdef />
-# </funcprototype>
-# </funcsynopsis>
-# <para>This function can be be optionally overridden by the user in their
-# test suite.</para>
-# <para>If this function exists, it will be called after each test completes.
-# It is useful to clean up the environment after each test.</para>
-# </entry>
-# </s:function>
-#*/
-# Note: see _shunit_mktempFunc() for actual implementation
-# tearDown() { :; }
-
-#------------------------------------------------------------------------------
-# internal shUnit2 functions
-#
-
-_shunit_cleanup()
-{
- name=$1
-
- case ${name} in
- EXIT) signal=0 ;;
- INT) signal=2 ;;
- TERM) signal=15 ;;
- esac
-
- # do our work
- rm -fr "${__shunit_tmpDir}"
-
- # exit for all non-EXIT signals
- if [ ${name} != 'EXIT' ]; then
- echo "trapped and now handling the ${name} signal" >&2
- _shunit_generateReport
- # disable EXIT trap
- trap 0
- # add 128 to signal and exit
- exit `expr ${signal} + 128`
- fi
-}
-
-_shunit_execSuite()
-{
- echo '#'
- echo '# Performing tests'
- echo '#'
- for _su_func in ${__shunit_suite}; do
- # execute the per-test setup function
- setUp
-
- # execute the test
- echo "${_su_func}"
- eval ${_su_func}
-
- # execute the per-test tear-down function
- tearDown
- done
-
- unset _su_func
-}
-
-_shunit_functionExists()
-{
- _su__func=$1
- type ${_su__func} 2>/dev/null |grep "is a function$" >/dev/null
- _su__return=$?
- unset _su__func
- return ${_su__return}
-}
-
-_shunit_generateReport()
-{
- _su__awkPercent='{printf("%0.0f%%", $1*100/$2)}'
- if [ ${__shunit_testsTotal} -gt 0 ]; then
- _su__success=`echo ${__shunit_testsPassed} ${__shunit_testsTotal} |\
- awk "${_su__awkPercent}"`
- else
- _su__success=0
- fi
-
- cat <<EOF
-
-#
-# Test report
-#
-tests passed: ${__shunit_testsPassed}
-tests failed: ${__shunit_testsFailed}
-tests total: ${__shunit_testsTotal}
-success rate: ${_su__success}
-EOF
-
- unset _su__success
-}
-
-# this function is a cross-platform temporary directory creation tool. not all
-# OSes have the mktemp function, so one is included here.
-_shunit_mktempDir()
-{
- # try the standard mktemp function
- ( exec mktemp -dqt shunit.XXXXXX 2>/dev/null ) && return
-
- # the standard mktemp didn't work. doing our own.
- if [ -r '/dev/urandom' -a -x '/usr/bin/od' ]; then
- _su__random=`/usr/bin/od -vAn -N4 -tx4 </dev/urandom \
- |sed 's/^[^0-9a-f]*//'`
- elif [ -n "${RANDOM:-}" ]; then
- # $RANDOM works
- _su__random=${RANDOM}${RANDOM}${RANDOM}$$
- else
- # $RANDOM doesn't work
- _su__date=`date '+%Y%m%d%H%M%S'`
- _su__random=`expr ${_su__date} / $$`
- fi
-
- _su__tmpDir="${TMPDIR-/tmp}/shunit.${_su__random}"
- ( umask 077 && mkdir "${_su__tmpDir}" ) || {
- echo 'shUnit:FATAL could not create temporary directory! exiting' >&2
- return ${__SHUNIT_ERROR}
- }
-
- echo ${_su__tmpDir}
- unset _su__date _su__random _su__tmpDir
-}
-
-# this function is here to work around issues in Cygwin
-_shunit_mktempFunc()
-{
- for _su__func in oneTimeSetUp oneTimeTearDown setUp tearDown suite; do
- _su__file="${__shunit_tmpDir}/${_su__func}"
- cat <<EOF >"${_su__file}"
-#! /bin/sh
-exit 0
-EOF
- chmod +x "${_su__file}"
- done
-
- unset _su__file
-}
-
-_shunit_testPassed()
-{
- __shunit_testsPassed=`expr ${__shunit_testsPassed} + 1`
- __shunit_testsTotal=`expr ${__shunit_testsTotal} + 1`
-}
-
-_shunit_testFailed()
-{
- _su__msg=$1
-
- __shunit_testsFailed=`expr ${__shunit_testsFailed} + 1`
- __shunit_testsTotal=`expr ${__shunit_testsTotal} + 1`
- echo "${__SHUNIT_ASSERT_MSG_PREFIX}${_su__msg}" >&2
-
- unset _su__msg
-}
-
-#------------------------------------------------------------------------------
-# main
-#
-
-# create a temporary storage location
-__shunit_tmpDir=`_shunit_mktempDir` || exit ${__SHUNIT_ERROR}
-
-# setup traps to clean up after ourselves
-trap '_shunit_cleanup EXIT' 0
-trap '_shunit_cleanup INT' 2
-trap '_shunit_cleanup TERM' 15
-
-# create phantom functions to work around issues with Cygwin
-_shunit_mktempFunc
-PATH="${__shunit_tmpDir}:${PATH}"
-
-# execute the oneTimeSetUp function (if it exists)
-#_shunit_functionExists oneTimeSetUp && oneTimeSetUp
-oneTimeSetUp
-
-# deprecated: execute the suite function defined in the parent test script
-suite
-
-# if no suite function was defined, dynamically build a list of functions
-if [ -z "${__shunit_suite}" ]; then
- funcs=`grep "^[ \t]*test[A-Za-z0-9_]* *()" $0 |sed 's/[^A-Za-z0-9_]//g'`
- for func in ${funcs}; do
- suite_addTest ${func}
- done
-fi
-
-# execute the tests
-_shunit_execSuite
-
-# execute the oneTimeTearDown function (if it exists)
-oneTimeTearDown
-
-# generate report
-_shunit_generateReport
-
-# restore the previous set of shell flags
-for _shunit_shellFlag in ${__SHUNIT_SHELL_FLAGS}; do
- echo ${__shunit_oldShellFlags} |grep ${_shunit_shellFlag} >/dev/null \
- || set +${_shunit_shellFlag}
-done
-unset _shunit_shellFlag
-
-#/**
-# </s:shelldoc>
-#*/
View it on GitLab: https://salsa.debian.org/med-team/sambamba/-/commit/83d2a9f492dd28cf97c1c2d02efc0fdfe1c1247a
--
View it on GitLab: https://salsa.debian.org/med-team/sambamba/-/commit/83d2a9f492dd28cf97c1c2d02efc0fdfe1c1247a
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-commit/attachments/20210720/3d260c33/attachment-0001.htm>
More information about the debian-med-commit
mailing list