forked from newville/ifeffit
-
Notifications
You must be signed in to change notification settings - Fork 0
/
COPYING
37 lines (30 loc) · 1.92 KB
/
COPYING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Copyright, Licensing, and Re-distribution
-----------------------------------------
Unless otherwise stated, the code in the Ifeffit distribution is
distributed under the following license:
Copyright (c) 1997--2000 Matthew Newville, The University of Chicago
Copyright (c) 1992--1996 Matthew Newville, University of Washington
Permission to use and redistribute the source code or binary forms of
this software and its documentation, with or without modification is
hereby granted provided that the above notice of copyright, these
terms of use, and the disclaimer of warranty below appear in the
source code and documentation, and that none of the names of The
University of Chicago, The University of Washington, or the authors
appear in advertising or endorsement of works derived from this
software without specific prior written permission from all parties.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THIS SOFTWARE.
A considerable portion of the code in this distribution is distributed
under the GNU Public License (GPL). Specifically, all code in the
readline/ subdirectory is taken from the GNU distribution, and is covered
by the GPL (see readline/COPYING). In addition, the code in src/cmdline
which uses the GNU Readline library is also distributed under the GPL.
Much of the code in the fortran/ subdirectory is distributed under a
BSD-like license from Bellcore/Lucent Technologies.
When in doubt, check the individual file for it's copyright and licensing
status or contact the authors.