qpdf-binary 12.4.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,66 @@
1
+ acl-libs-2.3.2-r1
2
+ alpine-baselayout-3.7.0-r0
3
+ alpine-baselayout-data-3.7.0-r0
4
+ alpine-keys-2.5-r0
5
+ alpine-release-3.22.8-r0
6
+ apk-tools-2.14.13-r0
7
+ binutils-2.44-r3
8
+ brotli-libs-1.1.1-r0
9
+ build-base-0.5-r3
10
+ busybox-1.37.0-r20
11
+ busybox-binsh-1.37.0-r20
12
+ c-ares-1.34.9-r0
13
+ ca-certificates-20261020-r0
14
+ ca-certificates-bundle-20261020-r0
15
+ cmake-3.31.7-r1
16
+ curl-8.14.1-r4
17
+ file-5.46-r2
18
+ fortify-headers-1.1-r5
19
+ g++-14.2.0-r6
20
+ gcc-14.2.0-r6
21
+ gmp-6.3.0-r3
22
+ isl26-0.26-r1
23
+ jansson-2.14.1-r0
24
+ libapk2-2.14.13-r0
25
+ libarchive-3.8.11-r0
26
+ libatomic-14.2.0-r6
27
+ libbz2-1.0.8-r6
28
+ libcrypto3-3.5.9-r0
29
+ libcurl-8.14.1-r4
30
+ libexpat-2.10.0-r0
31
+ libgcc-14.2.0-r6
32
+ libgomp-14.2.0-r6
33
+ libidn2-2.3.7-r0
34
+ libjpeg-turbo-3.1.0-r0
35
+ libjpeg-turbo-dev-3.1.0-r0
36
+ libjpeg-turbo-doc-3.1.0-r0
37
+ libjpeg-turbo-static-3.1.0-r0
38
+ libmagic-5.46-r2
39
+ libpsl-0.21.5-r3
40
+ libssl3-3.5.9-r0
41
+ libstdc++-14.2.0-r6
42
+ libstdc++-dev-14.2.0-r6
43
+ libturbojpeg-3.1.0-r0
44
+ libunistring-1.3-r0
45
+ libuv-1.51.0-r0
46
+ lz4-libs-1.10.0-r0
47
+ make-4.4.1-r3
48
+ mpc1-1.3.1-r1
49
+ mpfr4-4.2.1_p1-r0
50
+ musl-1.2.5-r13
51
+ musl-dev-1.2.5-r13
52
+ musl-utils-1.2.5-r13
53
+ nghttp2-libs-1.69.0-r0
54
+ openssl-dev-3.5.9-r0
55
+ openssl-libs-static-3.5.9-r0
56
+ patch-2.8-r0
57
+ pkgconf-2.4.3-r0
58
+ rhash-libs-1.4.5-r0
59
+ samurai-1.2-r7
60
+ scanelf-1.3.8-r1
61
+ ssl_client-1.37.0-r20
62
+ xz-libs-5.8.4-r0
63
+ zlib-1.4-r0
64
+ zlib-dev-1.4-r0
65
+ zlib-static-1.4-r0
66
+ zstd-libs-1.5.7-r0
Binary file
@@ -0,0 +1,135 @@
1
+ libjpeg-turbo Licenses
2
+ ======================
3
+
4
+ libjpeg-turbo is covered by two compatible BSD-style open source licenses:
5
+
6
+ - The IJG (Independent JPEG Group) License, which is listed in
7
+ [README.ijg](README.ijg)
8
+
9
+ This license applies to the libjpeg API library and associated programs,
10
+ including any code inherited from libjpeg and any modifications to that
11
+ code. Note that the libjpeg-turbo SIMD source code bears the
12
+ [zlib License](https://opensource.org/licenses/Zlib), but in the context of
13
+ the overall libjpeg API library, the terms of the zlib License are subsumed
14
+ by the terms of the IJG License.
15
+
16
+ - The Modified (3-clause) BSD License, which is listed below
17
+
18
+ This license applies to the TurboJPEG API library and associated programs, as
19
+ well as the build system. Note that the TurboJPEG API library wraps the
20
+ libjpeg API library, so in the context of the overall TurboJPEG API library,
21
+ both the terms of the IJG License and the terms of the Modified (3-clause)
22
+ BSD License apply.
23
+
24
+
25
+ Complying with the libjpeg-turbo Licenses
26
+ =========================================
27
+
28
+ This section provides a roll-up of the libjpeg-turbo licensing terms, to the
29
+ best of our understanding. This is not a license in and of itself. It is
30
+ intended solely for clarification.
31
+
32
+ 1. If you are distributing a modified version of the libjpeg-turbo source,
33
+ then:
34
+
35
+ 1. You cannot alter or remove any existing copyright or license notices
36
+ from the source.
37
+
38
+ **Origin**
39
+ - Clause 1 of the IJG License
40
+ - Clause 1 of the Modified BSD License
41
+ - Clauses 1 and 3 of the zlib License
42
+
43
+ 2. You must add your own copyright notice to the header of each source
44
+ file you modified, so others can tell that you modified that file. (If
45
+ there is not an existing copyright header in that file, then you can
46
+ simply add a notice stating that you modified the file.)
47
+
48
+ **Origin**
49
+ - Clause 1 of the IJG License
50
+ - Clause 2 of the zlib License
51
+
52
+ 3. You must include the IJG README file, and you must not alter any of the
53
+ copyright or license text in that file.
54
+
55
+ **Origin**
56
+ - Clause 1 of the IJG License
57
+
58
+ 2. If you are distributing only libjpeg-turbo binaries without the source, or
59
+ if you are distributing an application that statically links with
60
+ libjpeg-turbo, then:
61
+
62
+ 1. Your product documentation must include a message stating:
63
+
64
+ This software is based in part on the work of the Independent JPEG
65
+ Group.
66
+
67
+ **Origin**
68
+ - Clause 2 of the IJG license
69
+
70
+ 2. If your binary distribution includes or uses the TurboJPEG API, then
71
+ your product documentation must include the text of the Modified BSD
72
+ License (see below.)
73
+
74
+ **Origin**
75
+ - Clause 2 of the Modified BSD License
76
+
77
+ 3. You cannot use the name of the IJG or The libjpeg-turbo Project or the
78
+ contributors thereof in advertising, publicity, etc.
79
+
80
+ **Origin**
81
+ - IJG License
82
+ - Clause 3 of the Modified BSD License
83
+
84
+ 4. The IJG and The libjpeg-turbo Project do not warrant libjpeg-turbo to be
85
+ free of defects, nor do we accept any liability for undesirable
86
+ consequences resulting from your use of the software.
87
+
88
+ **Origin**
89
+ - IJG License
90
+ - Modified BSD License
91
+ - zlib License
92
+
93
+
94
+ The Modified (3-clause) BSD License
95
+ ===================================
96
+
97
+ Copyright (C)2009-2024 D. R. Commander. All Rights Reserved.<br>
98
+ Copyright (C)2015 Viktor Szathmáry. All Rights Reserved.
99
+
100
+ Redistribution and use in source and binary forms, with or without
101
+ modification, are permitted provided that the following conditions are met:
102
+
103
+ - Redistributions of source code must retain the above copyright notice,
104
+ this list of conditions and the following disclaimer.
105
+ - Redistributions in binary form must reproduce the above copyright notice,
106
+ this list of conditions and the following disclaimer in the documentation
107
+ and/or other materials provided with the distribution.
108
+ - Neither the name of the libjpeg-turbo Project nor the names of its
109
+ contributors may be used to endorse or promote products derived from this
110
+ software without specific prior written permission.
111
+
112
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS",
113
+ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
114
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
115
+ ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
116
+ LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
117
+ CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
118
+ SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
119
+ INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
120
+ CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
121
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
122
+ POSSIBILITY OF SUCH DAMAGE.
123
+
124
+
125
+ Why Two Licenses?
126
+ =================
127
+
128
+ The zlib License could have been used instead of the Modified (3-clause) BSD
129
+ License, and since the IJG License effectively subsumes the distribution
130
+ conditions of the zlib License, this would have effectively placed
131
+ libjpeg-turbo binary distributions under the IJG License. However, the IJG
132
+ License specifically refers to the Independent JPEG Group and does not extend
133
+ attribution and endorsement protections to other entities. Thus, it was
134
+ desirable to choose a license that granted us the same protections for new code
135
+ that were granted to the IJG for code derived from their software.
@@ -0,0 +1,260 @@
1
+ libjpeg-turbo note: This file has been modified by The libjpeg-turbo Project
2
+ to include only information relevant to libjpeg-turbo, to wordsmith certain
3
+ sections, and to remove impolitic language that existed in the libjpeg v8
4
+ README. It is included only for reference. Please see README.md for
5
+ information specific to libjpeg-turbo.
6
+
7
+
8
+ The Independent JPEG Group's JPEG software
9
+ ==========================================
10
+
11
+ This distribution contains a release of the Independent JPEG Group's free JPEG
12
+ software. You are welcome to redistribute this software and to use it for any
13
+ purpose, subject to the conditions under LEGAL ISSUES, below.
14
+
15
+ This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
16
+ Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
17
+ Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
18
+ and other members of the Independent JPEG Group.
19
+
20
+ IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee
21
+ (also known as JPEG, together with ITU-T SG16).
22
+
23
+
24
+ DOCUMENTATION ROADMAP
25
+ =====================
26
+
27
+ This file contains the following sections:
28
+
29
+ OVERVIEW General description of JPEG and the IJG software.
30
+ LEGAL ISSUES Copyright, lack of warranty, terms of distribution.
31
+ REFERENCES Where to learn more about JPEG.
32
+ ARCHIVE LOCATIONS Where to find newer versions of this software.
33
+ FILE FORMAT WARS Software *not* to get.
34
+ TO DO Plans for future IJG releases.
35
+
36
+ Other documentation files in the distribution are:
37
+
38
+ User documentation:
39
+ doc/usage.txt Usage instructions for cjpeg, djpeg, jpegtran,
40
+ rdjpgcom, and wrjpgcom.
41
+ doc/*.1 Unix-style man pages for programs (same info as
42
+ usage.txt).
43
+ doc/wizard.txt Advanced usage instructions for JPEG wizards only.
44
+ doc/change.log Version-to-version change highlights.
45
+ Programmer and internal documentation:
46
+ doc/libjpeg.txt How to use the JPEG library in your own programs.
47
+ src/example.c Sample code for calling the JPEG library.
48
+ doc/structure.txt Overview of the JPEG library's internal structure.
49
+ doc/coderules.txt Coding style rules --- please read if you contribute
50
+ code.
51
+
52
+ Please read at least usage.txt. Some information can also be found in the JPEG
53
+ FAQ (Frequently Asked Questions) article. See ARCHIVE LOCATIONS below to find
54
+ out where to obtain the FAQ article.
55
+
56
+ If you want to understand how the JPEG code works, we suggest reading one or
57
+ more of the REFERENCES, then looking at the documentation files (in roughly
58
+ the order listed) before diving into the code.
59
+
60
+
61
+ OVERVIEW
62
+ ========
63
+
64
+ This package contains C software to implement JPEG image encoding, decoding,
65
+ and transcoding. JPEG (pronounced "jay-peg") is a standardized compression
66
+ method for full-color and grayscale images. JPEG's strong suit is compressing
67
+ photographic images or other types of images that have smooth color and
68
+ brightness transitions between neighboring pixels. Images with sharp lines or
69
+ other abrupt features may not compress well with JPEG, and a higher JPEG
70
+ quality may have to be used to avoid visible compression artifacts with such
71
+ images.
72
+
73
+ JPEG is normally lossy, meaning that the output pixels are not necessarily
74
+ identical to the input pixels. However, on photographic content and other
75
+ "smooth" images, very good compression ratios can be obtained with no visible
76
+ compression artifacts, and extremely high compression ratios are possible if
77
+ you are willing to sacrifice image quality (by reducing the "quality" setting
78
+ in the compressor.)
79
+
80
+ This software implements JPEG baseline, extended-sequential, progressive, and
81
+ lossless compression processes. Provision is made for supporting all variants
82
+ of these processes, although some uncommon parameter settings aren't
83
+ implemented yet. We have made no provision for supporting the hierarchical
84
+ processes defined in the standard.
85
+
86
+ We provide a set of library routines for reading and writing JPEG image files,
87
+ plus two sample applications "cjpeg" and "djpeg", which use the library to
88
+ perform conversion between JPEG and some other popular image file formats.
89
+ The library is intended to be reused in other applications.
90
+
91
+ In order to support file conversion and viewing software, we have included
92
+ considerable functionality beyond the bare JPEG coding/decoding capability;
93
+ for example, the color quantization modules are not strictly part of JPEG
94
+ decoding, but they are essential for output to colormapped file formats. These
95
+ extra functions can be compiled out of the library if not required for a
96
+ particular application.
97
+
98
+ We have also included "jpegtran", a utility for lossless transcoding between
99
+ different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
100
+ applications for inserting and extracting textual comments in JFIF files.
101
+
102
+ The emphasis in designing this software has been on achieving portability and
103
+ flexibility, while also making it fast enough to be useful. In particular,
104
+ the software is not intended to be read as a tutorial on JPEG. (See the
105
+ REFERENCES section for introductory material.) Rather, it is intended to
106
+ be reliable, portable, industrial-strength code. We do not claim to have
107
+ achieved that goal in every aspect of the software, but we strive for it.
108
+
109
+ We welcome the use of this software as a component of commercial products.
110
+ No royalty is required, but we do ask for an acknowledgement in product
111
+ documentation, as described under LEGAL ISSUES.
112
+
113
+
114
+ LEGAL ISSUES
115
+ ============
116
+
117
+ In plain English:
118
+
119
+ 1. We don't promise that this software works. (But if you find any bugs,
120
+ please let us know!)
121
+ 2. You can use this software for whatever you want. You don't have to pay us.
122
+ 3. You may not pretend that you wrote this software. If you use it in a
123
+ program, you must acknowledge somewhere in your documentation that
124
+ you've used the IJG code.
125
+
126
+ In legalese:
127
+
128
+ The authors make NO WARRANTY or representation, either express or implied,
129
+ with respect to this software, its quality, accuracy, merchantability, or
130
+ fitness for a particular purpose. This software is provided "AS IS", and you,
131
+ its user, assume the entire risk as to its quality and accuracy.
132
+
133
+ This software is copyright (C) 1991-2020, Thomas G. Lane, Guido Vollbeding.
134
+ All Rights Reserved except as specified below.
135
+
136
+ Permission is hereby granted to use, copy, modify, and distribute this
137
+ software (or portions thereof) for any purpose, without fee, subject to these
138
+ conditions:
139
+ (1) If any part of the source code for this software is distributed, then this
140
+ README file must be included, with this copyright and no-warranty notice
141
+ unaltered; and any additions, deletions, or changes to the original files
142
+ must be clearly indicated in accompanying documentation.
143
+ (2) If only executable code is distributed, then the accompanying
144
+ documentation must state that "this software is based in part on the work of
145
+ the Independent JPEG Group".
146
+ (3) Permission for use of this software is granted only if the user accepts
147
+ full responsibility for any undesirable consequences; the authors accept
148
+ NO LIABILITY for damages of any kind.
149
+
150
+ These conditions apply to any software derived from or based on the IJG code,
151
+ not just to the unmodified library. If you use our work, you ought to
152
+ acknowledge us.
153
+
154
+ Permission is NOT granted for the use of any IJG author's name or company name
155
+ in advertising or publicity relating to this software or products derived from
156
+ it. This software may be referred to only as "the Independent JPEG Group's
157
+ software".
158
+
159
+ We specifically permit and encourage the use of this software as the basis of
160
+ commercial products, provided that all warranty or liability claims are
161
+ assumed by the product vendor.
162
+
163
+
164
+ REFERENCES
165
+ ==========
166
+
167
+ We recommend reading one or more of these references before trying to
168
+ understand the innards of the JPEG software.
169
+
170
+ The best short technical introduction to the JPEG compression algorithm is
171
+ Wallace, Gregory K. "The JPEG Still Picture Compression Standard",
172
+ Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
173
+ (Adjacent articles in that issue discuss MPEG motion picture compression,
174
+ applications of JPEG, and related topics.) If you don't have the CACM issue
175
+ handy, a PDF file containing a revised version of Wallace's article is
176
+ available at http://www.ijg.org/files/Wallace.JPEG.pdf. The file (actually
177
+ a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
178
+ omits the sample images that appeared in CACM, but it includes corrections
179
+ and some added material. Note: the Wallace article is copyright ACM and IEEE,
180
+ and it may not be used for commercial purposes.
181
+
182
+ A somewhat less technical, more leisurely introduction to JPEG can be found in
183
+ "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
184
+ M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides
185
+ good explanations and example C code for a multitude of compression methods
186
+ including JPEG. It is an excellent source if you are comfortable reading C
187
+ code but don't know much about data compression in general. The book's JPEG
188
+ sample code is far from industrial-strength, but when you are ready to look
189
+ at a full implementation, you've got one here...
190
+
191
+ The best currently available description of JPEG is the textbook "JPEG Still
192
+ Image Data Compression Standard" by William B. Pennebaker and Joan L.
193
+ Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
194
+ Price US$59.95, 638 pp. The book includes the complete text of the ISO JPEG
195
+ standards (DIS 10918-1 and draft DIS 10918-2).
196
+
197
+ The original JPEG standard is divided into two parts, Part 1 being the actual
198
+ specification, while Part 2 covers compliance testing methods. Part 1 is
199
+ titled "Digital Compression and Coding of Continuous-tone Still Images,
200
+ Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
201
+ 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of
202
+ Continuous-tone Still Images, Part 2: Compliance testing" and has document
203
+ numbers ISO/IEC IS 10918-2, ITU-T T.83.
204
+
205
+ The JPEG standard does not specify all details of an interchangeable file
206
+ format. For the omitted details, we follow the "JFIF" conventions, revision
207
+ 1.02. JFIF version 1 has been adopted as ISO/IEC 10918-5 (05/2013) and
208
+ Recommendation ITU-T T.871 (05/2011): Information technology - Digital
209
+ compression and coding of continuous-tone still images: JPEG File Interchange
210
+ Format (JFIF). It is available as a free download in PDF file format from
211
+ https://www.iso.org/standard/54989.html and http://www.itu.int/rec/T-REC-T.871.
212
+ A PDF file of the older JFIF 1.02 specification is available at
213
+ http://www.w3.org/Graphics/JPEG/jfif3.pdf.
214
+
215
+ The TIFF 6.0 file format specification can be obtained from
216
+ http://mirrors.ctan.org/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation
217
+ scheme found in the TIFF 6.0 spec of 3-June-92 has a number of serious
218
+ problems. IJG does not recommend use of the TIFF 6.0 design (TIFF Compression
219
+ tag 6). Instead, we recommend the JPEG design proposed by TIFF Technical Note
220
+ #2 (Compression tag 7). Copies of this Note can be obtained from
221
+ http://www.ijg.org/files/. It is expected that the next revision
222
+ of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
223
+ Although IJG's own code does not support TIFF/JPEG, the free libtiff library
224
+ uses our library to implement TIFF/JPEG per the Note.
225
+
226
+
227
+ ARCHIVE LOCATIONS
228
+ =================
229
+
230
+ The "official" archive site for this software is www.ijg.org.
231
+ The most recent released version can always be found there in
232
+ directory "files".
233
+
234
+ The JPEG FAQ (Frequently Asked Questions) article is a source of some
235
+ general information about JPEG. It is available at
236
+ http://www.faqs.org/faqs/jpeg-faq.
237
+
238
+
239
+ FILE FORMAT COMPATIBILITY
240
+ =========================
241
+
242
+ This software implements ITU T.81 | ISO/IEC 10918 with some extensions from
243
+ ITU T.871 | ISO/IEC 10918-5 (JPEG File Interchange Format-- see REFERENCES).
244
+ Informally, the term "JPEG image" or "JPEG file" most often refers to JFIF or
245
+ a subset thereof, but there are other formats containing the name "JPEG" that
246
+ are incompatible with the original JPEG standard or with JFIF (for instance,
247
+ JPEG 2000 and JPEG XR). This software therefore does not support these
248
+ formats. Indeed, one of the original reasons for developing this free software
249
+ was to help force convergence on a common, interoperable format standard for
250
+ JPEG files.
251
+
252
+ JFIF is a minimal or "low end" representation. TIFF/JPEG (TIFF revision 6.0 as
253
+ modified by TIFF Technical Note #2) can be used for "high end" applications
254
+ that need to record a lot of additional data about an image.
255
+
256
+
257
+ TO DO
258
+ =====
259
+
260
+ Please send bug reports, offers of help, etc. to jpeg-info@jpegclub.org.
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.