summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/LPPL-1.0
diff options
context:
space:
mode:
authorTudor Florea <tudor.florea@enea.com>2014-10-16 03:05:19 +0200
committerTudor Florea <tudor.florea@enea.com>2014-10-16 03:05:19 +0200
commitc527fd1f14c27855a37f2e8ac5346ce8d940ced2 (patch)
treebb002c1fdf011c41dbd2f0927bed23ecb5f83c97 /meta/files/common-licenses/LPPL-1.0
downloadpoky-daisy-140929.tar.gz
initial commit for Enea Linux 4.0-140929daisy-140929
Migrated from the internal git server on the daisy-enea-point-release branch Signed-off-by: Tudor Florea <tudor.florea@enea.com>
Diffstat (limited to 'meta/files/common-licenses/LPPL-1.0')
-rw-r--r--meta/files/common-licenses/LPPL-1.0213
1 files changed, 213 insertions, 0 deletions
diff --git a/meta/files/common-licenses/LPPL-1.0 b/meta/files/common-licenses/LPPL-1.0
new file mode 100644
index 0000000000..f9ef35d798
--- /dev/null
+++ b/meta/files/common-licenses/LPPL-1.0
@@ -0,0 +1,213 @@
1
2LaTeX Project Public License
3============================
4
5LPPL Version 1.0 1999-03-01
6
7Copyright 1999 LaTeX3 Project
8 Everyone is permitted to copy and distribute verbatim copies
9 of this license document, but modification is not allowed.
10
11
12Preamble
13========
14
15The LaTeX Project Public License (LPPL) is the license under which the
16base LaTeX distribution is distributed. As described below you may use
17this licence for any software that you wish to distribute.
18
19It may be particularly suitable if your software is TeX related (such
20as a LaTeX package file) but it may be used for any software, even if
21it is unrelated to TeX.
22
23To use this license, the files of your distribution should have an
24explicit copyright notice giving your name and the year, together
25with a reference to this license.
26
27A typical example would be
28
29 %% pig.sty
30 %% Copyright 2001 M. Y. Name
31
32 % This program can redistributed and/or modified under the terms
33 % of the LaTeX Project Public License Distributed from CTAN
34 % archives in directory macros/latex/base/lppl.txt; either
35 % version 1 of the License, or (at your option) any later version.
36
37Given such a notice in the file, the conditions of this document would
38apply, with:
39
40`The Program` referring to the software `pig.sty` and
41`The Copyright Holder` referring to the person `M. Y. Name`.
42
43To see a real example, see the file legal.txt which carries the
44copyright notice for the base latex distribution.
45
46This license gives terms under which files of The Program may be
47distributed and modified. Individual files may have specific further
48constraints on modification, but no file should have restrictions on
49distribution other than those specified below.
50This is to ensure that a distributor wishing to distribute a complete
51unmodified copy of The Program need only check the conditions in this
52file, and does not need to check every file in The Program for extra
53restrictions. If you do need to modify the distribution terms of some
54files, do not refer to this license, instead distribute The Program
55under a different license. You may use the parts of the text of LPPL as
56a model for your own license, but your license should not directly refer
57to the LPPL or otherwise give the impression that The Program is
58distributed under the LPPL.
59
60
61
62The LaTeX Project Public License
63================================
64Terms And Conditions For Copying, Distribution And Modification
65===============================================================
66
67
68WARRANTY
69========
70
71There is no warranty for The Program, to the extent permitted by
72applicable law. Except when otherwise stated in writing, The
73Copyright Holder provides The Program `as is` without warranty of any
74kind, either expressed or implied, including, but not limited to, the
75implied warranties of merchantability and fitness for a particular
76purpose. The entire risk as to the quality and performance of the
77program is with you. Should The Program prove defective, you assume
78the cost of all necessary servicing, repair or correction.
79
80In no event unless required by applicable law or agreed to in writing
81will The Copyright Holder, or any of the individual authors named in
82the source for The Program, be liable to you for damages, including
83any general, special, incidental or consequential damages arising out
84of any use of The Program or out of inability to use The Program
85(including but not limited to loss of data or data being rendered
86inaccurate or losses sustained by you or by third parties as a result
87of a failure of The Program to operate with any other programs), even
88if such holder or other party has been advised of the possibility of
89such damages.
90
91
92DISTRIBUTION
93============
94
95Redistribution of unchanged files is allowed provided that all files
96that make up the distribution of The Program are distributed.
97In particular this means that The Program has to be distributed
98including its documentation if documentation was part of the original
99distribution.
100
101The distribution of The Program will contain a prominent file
102listing all the files covered by this license.
103
104If you receive only some of these files from someone, complain!
105
106The distribution of changed versions of certain files included in the
107The Program, and the reuse of code from The Program, are allowed
108under the following restrictions:
109
110 * It is allowed only if the legal notice in the file does not
111 expressly forbid it.
112 See note below, under "Conditions on individual files".
113
114 * You rename the file before you make any changes to it, unless the
115 file explicitly says that renaming is not required. Any such changed
116 files must be distributed under a license that forbids distribution
117 of those files, and any files derived from them, under the names used
118 by the original files in the distribution of The Program.
119
120 * You change any `identification string` in The Program to clearly
121 indicate that the file is not part of the standard system.
122
123 * If The Program includes an `error report address` so that errors
124 may be reported to The Copyright Holder, or other specified
125 addresses, this address must be changed in any modified versions of
126 The Program, so that reports for files not maintained by the
127 original program maintainers are directed to the maintainers of the
128 changed files.
129
130 * You acknowledge the source and authorship of the original version
131 in the modified file.
132
133 * You also distribute the unmodified version of the file or
134 alternatively provide sufficient information so that the
135 user of your modified file can be reasonably expected to be
136 able to obtain an original, unmodified copy of The Program.
137 For example, you may specify a URL to a site that you expect
138 will freely provide the user with a copy of The Program (either
139 the version on which your modification is based, or perhaps a
140 later version).
141
142 * If The Program is intended to be used with, or is based on, LaTeX,
143 then files with the following file extensions which have special
144 meaning in LaTeX Software, have special modification rules under the
145 license:
146
147 - Files with extension `.ins` (installation files): these files may
148 not be modified at all because they contain the legal notices
149 that are placed in the generated files.
150
151 - Files with extension `.fd` (LaTeX font definitions files): these
152 files are allowed to be modified without changing the name, but
153 only to enable use of all available fonts and to prevent attempts
154 to access unavailable fonts. However, modified files are not
155 allowed to be distributed in place of original files.
156
157 - Files with extension `.cfg` (configuration files): these files
158 can be created or modified to enable easy configuration of the
159 system. The documentation in cfgguide.tex in the base LaTeX
160 distribution describes when it makes sense to modify or generate
161 such files.
162
163
164The above restrictions are not intended to prohibit, and hence do
165not apply to, the updating, by any method, of a file so that it
166becomes identical to the latest version of that file in The Program.
167
168========================================================================
169
170NOTES
171=====
172
173We believe that these requirements give you the freedom you to make
174modifications that conform with whatever technical specifications you
175wish, whilst maintaining the availability, integrity and reliability of
176The Program. If you do not see how to achieve your goal whilst
177adhering to these requirements then read the document cfgguide.tex
178in the base LaTeX distribution for suggestions.
179
180Because of the portability and exchangeability aspects of systems
181like LaTeX, The LaTeX3 Project deprecates the distribution of
182non-standard versions of components of LaTeX or of generally available
183contributed code for them but such distributions are permitted under the
184above restrictions.
185
186The document modguide.tex in the base LaTeX distribution details
187the reasons for the legal requirements detailed above.
188Even if The Program is unrelated to LaTeX, the argument in
189modguide.tex may still apply, and should be read before
190a modified version of The Program is distributed.
191
192
193Conditions on individual files
194==============================
195
196The individual files may bear additional conditions which supersede
197the general conditions on distribution and modification contained in
198this file. If there are any such files, the distribution of The
199Program will contain a prominent file that lists all the exceptional
200files.
201
202Typical examples of files with more restrictive modification
203conditions would be files that contain the text of copyright notices.
204
205 * The conditions on individual files differ only in the
206 extent of *modification* that is allowed.
207
208 * The conditions on *distribution* are the same for all the files.
209 Thus a (re)distributor of a complete, unchanged copy of The Program
210 need meet only the conditions in this file; it is not necessary to
211 check the header of every file in the distribution to check that a
212 distribution meets these requirements.
213