1 |
commit: 86dbd440641d5e12dbe9da663676ed861a25205b |
2 |
Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org> |
3 |
AuthorDate: Wed Dec 28 18:14:21 2011 +0000 |
4 |
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org> |
5 |
CommitDate: Wed Dec 28 18:14:21 2011 +0000 |
6 |
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/elfix.git;a=commit;h=86dbd440 |
7 |
|
8 |
misc/test-revdep-pax: test package for revdep-pax |
9 |
|
10 |
--- |
11 |
misc/test-revdep-pax/COPYING | 674 +++++++++++++++++++++++++ |
12 |
misc/test-revdep-pax/INSTALL | 365 +++++++++++++ |
13 |
misc/test-revdep-pax/Makefile.am | 10 + |
14 |
misc/test-revdep-pax/README | 35 ++ |
15 |
misc/test-revdep-pax/autogen.sh | 7 + |
16 |
misc/test-revdep-pax/configure.ac | 18 + |
17 |
misc/test-revdep-pax/libmyrevdeppax.c | 5 + |
18 |
misc/test-revdep-pax/testrevdeppax-0.1.ebuild | 17 + |
19 |
misc/test-revdep-pax/testrevdeppax.c | 5 + |
20 |
misc/test-revdep-pax/testrevdeppax.sh | 3 + |
21 |
10 files changed, 1139 insertions(+), 0 deletions(-) |
22 |
|
23 |
diff --git a/misc/test-revdep-pax/COPYING b/misc/test-revdep-pax/COPYING |
24 |
new file mode 100644 |
25 |
index 0000000..94a9ed0 |
26 |
--- /dev/null |
27 |
+++ b/misc/test-revdep-pax/COPYING |
28 |
@@ -0,0 +1,674 @@ |
29 |
+ GNU GENERAL PUBLIC LICENSE |
30 |
+ Version 3, 29 June 2007 |
31 |
+ |
32 |
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> |
33 |
+ Everyone is permitted to copy and distribute verbatim copies |
34 |
+ of this license document, but changing it is not allowed. |
35 |
+ |
36 |
+ Preamble |
37 |
+ |
38 |
+ The GNU General Public License is a free, copyleft license for |
39 |
+software and other kinds of works. |
40 |
+ |
41 |
+ The licenses for most software and other practical works are designed |
42 |
+to take away your freedom to share and change the works. By contrast, |
43 |
+the GNU General Public License is intended to guarantee your freedom to |
44 |
+share and change all versions of a program--to make sure it remains free |
45 |
+software for all its users. We, the Free Software Foundation, use the |
46 |
+GNU General Public License for most of our software; it applies also to |
47 |
+any other work released this way by its authors. You can apply it to |
48 |
+your programs, too. |
49 |
+ |
50 |
+ When we speak of free software, we are referring to freedom, not |
51 |
+price. Our General Public Licenses are designed to make sure that you |
52 |
+have the freedom to distribute copies of free software (and charge for |
53 |
+them if you wish), that you receive source code or can get it if you |
54 |
+want it, that you can change the software or use pieces of it in new |
55 |
+free programs, and that you know you can do these things. |
56 |
+ |
57 |
+ To protect your rights, we need to prevent others from denying you |
58 |
+these rights or asking you to surrender the rights. Therefore, you have |
59 |
+certain responsibilities if you distribute copies of the software, or if |
60 |
+you modify it: responsibilities to respect the freedom of others. |
61 |
+ |
62 |
+ For example, if you distribute copies of such a program, whether |
63 |
+gratis or for a fee, you must pass on to the recipients the same |
64 |
+freedoms that you received. You must make sure that they, too, receive |
65 |
+or can get the source code. And you must show them these terms so they |
66 |
+know their rights. |
67 |
+ |
68 |
+ Developers that use the GNU GPL protect your rights with two steps: |
69 |
+(1) assert copyright on the software, and (2) offer you this License |
70 |
+giving you legal permission to copy, distribute and/or modify it. |
71 |
+ |
72 |
+ For the developers' and authors' protection, the GPL clearly explains |
73 |
+that there is no warranty for this free software. For both users' and |
74 |
+authors' sake, the GPL requires that modified versions be marked as |
75 |
+changed, so that their problems will not be attributed erroneously to |
76 |
+authors of previous versions. |
77 |
+ |
78 |
+ Some devices are designed to deny users access to install or run |
79 |
+modified versions of the software inside them, although the manufacturer |
80 |
+can do so. This is fundamentally incompatible with the aim of |
81 |
+protecting users' freedom to change the software. The systematic |
82 |
+pattern of such abuse occurs in the area of products for individuals to |
83 |
+use, which is precisely where it is most unacceptable. Therefore, we |
84 |
+have designed this version of the GPL to prohibit the practice for those |
85 |
+products. If such problems arise substantially in other domains, we |
86 |
+stand ready to extend this provision to those domains in future versions |
87 |
+of the GPL, as needed to protect the freedom of users. |
88 |
+ |
89 |
+ Finally, every program is threatened constantly by software patents. |
90 |
+States should not allow patents to restrict development and use of |
91 |
+software on general-purpose computers, but in those that do, we wish to |
92 |
+avoid the special danger that patents applied to a free program could |
93 |
+make it effectively proprietary. To prevent this, the GPL assures that |
94 |
+patents cannot be used to render the program non-free. |
95 |
+ |
96 |
+ The precise terms and conditions for copying, distribution and |
97 |
+modification follow. |
98 |
+ |
99 |
+ TERMS AND CONDITIONS |
100 |
+ |
101 |
+ 0. Definitions. |
102 |
+ |
103 |
+ "This License" refers to version 3 of the GNU General Public License. |
104 |
+ |
105 |
+ "Copyright" also means copyright-like laws that apply to other kinds of |
106 |
+works, such as semiconductor masks. |
107 |
+ |
108 |
+ "The Program" refers to any copyrightable work licensed under this |
109 |
+License. Each licensee is addressed as "you". "Licensees" and |
110 |
+"recipients" may be individuals or organizations. |
111 |
+ |
112 |
+ To "modify" a work means to copy from or adapt all or part of the work |
113 |
+in a fashion requiring copyright permission, other than the making of an |
114 |
+exact copy. The resulting work is called a "modified version" of the |
115 |
+earlier work or a work "based on" the earlier work. |
116 |
+ |
117 |
+ A "covered work" means either the unmodified Program or a work based |
118 |
+on the Program. |
119 |
+ |
120 |
+ To "propagate" a work means to do anything with it that, without |
121 |
+permission, would make you directly or secondarily liable for |
122 |
+infringement under applicable copyright law, except executing it on a |
123 |
+computer or modifying a private copy. Propagation includes copying, |
124 |
+distribution (with or without modification), making available to the |
125 |
+public, and in some countries other activities as well. |
126 |
+ |
127 |
+ To "convey" a work means any kind of propagation that enables other |
128 |
+parties to make or receive copies. Mere interaction with a user through |
129 |
+a computer network, with no transfer of a copy, is not conveying. |
130 |
+ |
131 |
+ An interactive user interface displays "Appropriate Legal Notices" |
132 |
+to the extent that it includes a convenient and prominently visible |
133 |
+feature that (1) displays an appropriate copyright notice, and (2) |
134 |
+tells the user that there is no warranty for the work (except to the |
135 |
+extent that warranties are provided), that licensees may convey the |
136 |
+work under this License, and how to view a copy of this License. If |
137 |
+the interface presents a list of user commands or options, such as a |
138 |
+menu, a prominent item in the list meets this criterion. |
139 |
+ |
140 |
+ 1. Source Code. |
141 |
+ |
142 |
+ The "source code" for a work means the preferred form of the work |
143 |
+for making modifications to it. "Object code" means any non-source |
144 |
+form of a work. |
145 |
+ |
146 |
+ A "Standard Interface" means an interface that either is an official |
147 |
+standard defined by a recognized standards body, or, in the case of |
148 |
+interfaces specified for a particular programming language, one that |
149 |
+is widely used among developers working in that language. |
150 |
+ |
151 |
+ The "System Libraries" of an executable work include anything, other |
152 |
+than the work as a whole, that (a) is included in the normal form of |
153 |
+packaging a Major Component, but which is not part of that Major |
154 |
+Component, and (b) serves only to enable use of the work with that |
155 |
+Major Component, or to implement a Standard Interface for which an |
156 |
+implementation is available to the public in source code form. A |
157 |
+"Major Component", in this context, means a major essential component |
158 |
+(kernel, window system, and so on) of the specific operating system |
159 |
+(if any) on which the executable work runs, or a compiler used to |
160 |
+produce the work, or an object code interpreter used to run it. |
161 |
+ |
162 |
+ The "Corresponding Source" for a work in object code form means all |
163 |
+the source code needed to generate, install, and (for an executable |
164 |
+work) run the object code and to modify the work, including scripts to |
165 |
+control those activities. However, it does not include the work's |
166 |
+System Libraries, or general-purpose tools or generally available free |
167 |
+programs which are used unmodified in performing those activities but |
168 |
+which are not part of the work. For example, Corresponding Source |
169 |
+includes interface definition files associated with source files for |
170 |
+the work, and the source code for shared libraries and dynamically |
171 |
+linked subprograms that the work is specifically designed to require, |
172 |
+such as by intimate data communication or control flow between those |
173 |
+subprograms and other parts of the work. |
174 |
+ |
175 |
+ The Corresponding Source need not include anything that users |
176 |
+can regenerate automatically from other parts of the Corresponding |
177 |
+Source. |
178 |
+ |
179 |
+ The Corresponding Source for a work in source code form is that |
180 |
+same work. |
181 |
+ |
182 |
+ 2. Basic Permissions. |
183 |
+ |
184 |
+ All rights granted under this License are granted for the term of |
185 |
+copyright on the Program, and are irrevocable provided the stated |
186 |
+conditions are met. This License explicitly affirms your unlimited |
187 |
+permission to run the unmodified Program. The output from running a |
188 |
+covered work is covered by this License only if the output, given its |
189 |
+content, constitutes a covered work. This License acknowledges your |
190 |
+rights of fair use or other equivalent, as provided by copyright law. |
191 |
+ |
192 |
+ You may make, run and propagate covered works that you do not |
193 |
+convey, without conditions so long as your license otherwise remains |
194 |
+in force. You may convey covered works to others for the sole purpose |
195 |
+of having them make modifications exclusively for you, or provide you |
196 |
+with facilities for running those works, provided that you comply with |
197 |
+the terms of this License in conveying all material for which you do |
198 |
+not control copyright. Those thus making or running the covered works |
199 |
+for you must do so exclusively on your behalf, under your direction |
200 |
+and control, on terms that prohibit them from making any copies of |
201 |
+your copyrighted material outside their relationship with you. |
202 |
+ |
203 |
+ Conveying under any other circumstances is permitted solely under |
204 |
+the conditions stated below. Sublicensing is not allowed; section 10 |
205 |
+makes it unnecessary. |
206 |
+ |
207 |
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law. |
208 |
+ |
209 |
+ No covered work shall be deemed part of an effective technological |
210 |
+measure under any applicable law fulfilling obligations under article |
211 |
+11 of the WIPO copyright treaty adopted on 20 December 1996, or |
212 |
+similar laws prohibiting or restricting circumvention of such |
213 |
+measures. |
214 |
+ |
215 |
+ When you convey a covered work, you waive any legal power to forbid |
216 |
+circumvention of technological measures to the extent such circumvention |
217 |
+is effected by exercising rights under this License with respect to |
218 |
+the covered work, and you disclaim any intention to limit operation or |
219 |
+modification of the work as a means of enforcing, against the work's |
220 |
+users, your or third parties' legal rights to forbid circumvention of |
221 |
+technological measures. |
222 |
+ |
223 |
+ 4. Conveying Verbatim Copies. |
224 |
+ |
225 |
+ You may convey verbatim copies of the Program's source code as you |
226 |
+receive it, in any medium, provided that you conspicuously and |
227 |
+appropriately publish on each copy an appropriate copyright notice; |
228 |
+keep intact all notices stating that this License and any |
229 |
+non-permissive terms added in accord with section 7 apply to the code; |
230 |
+keep intact all notices of the absence of any warranty; and give all |
231 |
+recipients a copy of this License along with the Program. |
232 |
+ |
233 |
+ You may charge any price or no price for each copy that you convey, |
234 |
+and you may offer support or warranty protection for a fee. |
235 |
+ |
236 |
+ 5. Conveying Modified Source Versions. |
237 |
+ |
238 |
+ You may convey a work based on the Program, or the modifications to |
239 |
+produce it from the Program, in the form of source code under the |
240 |
+terms of section 4, provided that you also meet all of these conditions: |
241 |
+ |
242 |
+ a) The work must carry prominent notices stating that you modified |
243 |
+ it, and giving a relevant date. |
244 |
+ |
245 |
+ b) The work must carry prominent notices stating that it is |
246 |
+ released under this License and any conditions added under section |
247 |
+ 7. This requirement modifies the requirement in section 4 to |
248 |
+ "keep intact all notices". |
249 |
+ |
250 |
+ c) You must license the entire work, as a whole, under this |
251 |
+ License to anyone who comes into possession of a copy. This |
252 |
+ License will therefore apply, along with any applicable section 7 |
253 |
+ additional terms, to the whole of the work, and all its parts, |
254 |
+ regardless of how they are packaged. This License gives no |
255 |
+ permission to license the work in any other way, but it does not |
256 |
+ invalidate such permission if you have separately received it. |
257 |
+ |
258 |
+ d) If the work has interactive user interfaces, each must display |
259 |
+ Appropriate Legal Notices; however, if the Program has interactive |
260 |
+ interfaces that do not display Appropriate Legal Notices, your |
261 |
+ work need not make them do so. |
262 |
+ |
263 |
+ A compilation of a covered work with other separate and independent |
264 |
+works, which are not by their nature extensions of the covered work, |
265 |
+and which are not combined with it such as to form a larger program, |
266 |
+in or on a volume of a storage or distribution medium, is called an |
267 |
+"aggregate" if the compilation and its resulting copyright are not |
268 |
+used to limit the access or legal rights of the compilation's users |
269 |
+beyond what the individual works permit. Inclusion of a covered work |
270 |
+in an aggregate does not cause this License to apply to the other |
271 |
+parts of the aggregate. |
272 |
+ |
273 |
+ 6. Conveying Non-Source Forms. |
274 |
+ |
275 |
+ You may convey a covered work in object code form under the terms |
276 |
+of sections 4 and 5, provided that you also convey the |
277 |
+machine-readable Corresponding Source under the terms of this License, |
278 |
+in one of these ways: |
279 |
+ |
280 |
+ a) Convey the object code in, or embodied in, a physical product |
281 |
+ (including a physical distribution medium), accompanied by the |
282 |
+ Corresponding Source fixed on a durable physical medium |
283 |
+ customarily used for software interchange. |
284 |
+ |
285 |
+ b) Convey the object code in, or embodied in, a physical product |
286 |
+ (including a physical distribution medium), accompanied by a |
287 |
+ written offer, valid for at least three years and valid for as |
288 |
+ long as you offer spare parts or customer support for that product |
289 |
+ model, to give anyone who possesses the object code either (1) a |
290 |
+ copy of the Corresponding Source for all the software in the |
291 |
+ product that is covered by this License, on a durable physical |
292 |
+ medium customarily used for software interchange, for a price no |
293 |
+ more than your reasonable cost of physically performing this |
294 |
+ conveying of source, or (2) access to copy the |
295 |
+ Corresponding Source from a network server at no charge. |
296 |
+ |
297 |
+ c) Convey individual copies of the object code with a copy of the |
298 |
+ written offer to provide the Corresponding Source. This |
299 |
+ alternative is allowed only occasionally and noncommercially, and |
300 |
+ only if you received the object code with such an offer, in accord |
301 |
+ with subsection 6b. |
302 |
+ |
303 |
+ d) Convey the object code by offering access from a designated |
304 |
+ place (gratis or for a charge), and offer equivalent access to the |
305 |
+ Corresponding Source in the same way through the same place at no |
306 |
+ further charge. You need not require recipients to copy the |
307 |
+ Corresponding Source along with the object code. If the place to |
308 |
+ copy the object code is a network server, the Corresponding Source |
309 |
+ may be on a different server (operated by you or a third party) |
310 |
+ that supports equivalent copying facilities, provided you maintain |
311 |
+ clear directions next to the object code saying where to find the |
312 |
+ Corresponding Source. Regardless of what server hosts the |
313 |
+ Corresponding Source, you remain obligated to ensure that it is |
314 |
+ available for as long as needed to satisfy these requirements. |
315 |
+ |
316 |
+ e) Convey the object code using peer-to-peer transmission, provided |
317 |
+ you inform other peers where the object code and Corresponding |
318 |
+ Source of the work are being offered to the general public at no |
319 |
+ charge under subsection 6d. |
320 |
+ |
321 |
+ A separable portion of the object code, whose source code is excluded |
322 |
+from the Corresponding Source as a System Library, need not be |
323 |
+included in conveying the object code work. |
324 |
+ |
325 |
+ A "User Product" is either (1) a "consumer product", which means any |
326 |
+tangible personal property which is normally used for personal, family, |
327 |
+or household purposes, or (2) anything designed or sold for incorporation |
328 |
+into a dwelling. In determining whether a product is a consumer product, |
329 |
+doubtful cases shall be resolved in favor of coverage. For a particular |
330 |
+product received by a particular user, "normally used" refers to a |
331 |
+typical or common use of that class of product, regardless of the status |
332 |
+of the particular user or of the way in which the particular user |
333 |
+actually uses, or expects or is expected to use, the product. A product |
334 |
+is a consumer product regardless of whether the product has substantial |
335 |
+commercial, industrial or non-consumer uses, unless such uses represent |
336 |
+the only significant mode of use of the product. |
337 |
+ |
338 |
+ "Installation Information" for a User Product means any methods, |
339 |
+procedures, authorization keys, or other information required to install |
340 |
+and execute modified versions of a covered work in that User Product from |
341 |
+a modified version of its Corresponding Source. The information must |
342 |
+suffice to ensure that the continued functioning of the modified object |
343 |
+code is in no case prevented or interfered with solely because |
344 |
+modification has been made. |
345 |
+ |
346 |
+ If you convey an object code work under this section in, or with, or |
347 |
+specifically for use in, a User Product, and the conveying occurs as |
348 |
+part of a transaction in which the right of possession and use of the |
349 |
+User Product is transferred to the recipient in perpetuity or for a |
350 |
+fixed term (regardless of how the transaction is characterized), the |
351 |
+Corresponding Source conveyed under this section must be accompanied |
352 |
+by the Installation Information. But this requirement does not apply |
353 |
+if neither you nor any third party retains the ability to install |
354 |
+modified object code on the User Product (for example, the work has |
355 |
+been installed in ROM). |
356 |
+ |
357 |
+ The requirement to provide Installation Information does not include a |
358 |
+requirement to continue to provide support service, warranty, or updates |
359 |
+for a work that has been modified or installed by the recipient, or for |
360 |
+the User Product in which it has been modified or installed. Access to a |
361 |
+network may be denied when the modification itself materially and |
362 |
+adversely affects the operation of the network or violates the rules and |
363 |
+protocols for communication across the network. |
364 |
+ |
365 |
+ Corresponding Source conveyed, and Installation Information provided, |
366 |
+in accord with this section must be in a format that is publicly |
367 |
+documented (and with an implementation available to the public in |
368 |
+source code form), and must require no special password or key for |
369 |
+unpacking, reading or copying. |
370 |
+ |
371 |
+ 7. Additional Terms. |
372 |
+ |
373 |
+ "Additional permissions" are terms that supplement the terms of this |
374 |
+License by making exceptions from one or more of its conditions. |
375 |
+Additional permissions that are applicable to the entire Program shall |
376 |
+be treated as though they were included in this License, to the extent |
377 |
+that they are valid under applicable law. If additional permissions |
378 |
+apply only to part of the Program, that part may be used separately |
379 |
+under those permissions, but the entire Program remains governed by |
380 |
+this License without regard to the additional permissions. |
381 |
+ |
382 |
+ When you convey a copy of a covered work, you may at your option |
383 |
+remove any additional permissions from that copy, or from any part of |
384 |
+it. (Additional permissions may be written to require their own |
385 |
+removal in certain cases when you modify the work.) You may place |
386 |
+additional permissions on material, added by you to a covered work, |
387 |
+for which you have or can give appropriate copyright permission. |
388 |
+ |
389 |
+ Notwithstanding any other provision of this License, for material you |
390 |
+add to a covered work, you may (if authorized by the copyright holders of |
391 |
+that material) supplement the terms of this License with terms: |
392 |
+ |
393 |
+ a) Disclaiming warranty or limiting liability differently from the |
394 |
+ terms of sections 15 and 16 of this License; or |
395 |
+ |
396 |
+ b) Requiring preservation of specified reasonable legal notices or |
397 |
+ author attributions in that material or in the Appropriate Legal |
398 |
+ Notices displayed by works containing it; or |
399 |
+ |
400 |
+ c) Prohibiting misrepresentation of the origin of that material, or |
401 |
+ requiring that modified versions of such material be marked in |
402 |
+ reasonable ways as different from the original version; or |
403 |
+ |
404 |
+ d) Limiting the use for publicity purposes of names of licensors or |
405 |
+ authors of the material; or |
406 |
+ |
407 |
+ e) Declining to grant rights under trademark law for use of some |
408 |
+ trade names, trademarks, or service marks; or |
409 |
+ |
410 |
+ f) Requiring indemnification of licensors and authors of that |
411 |
+ material by anyone who conveys the material (or modified versions of |
412 |
+ it) with contractual assumptions of liability to the recipient, for |
413 |
+ any liability that these contractual assumptions directly impose on |
414 |
+ those licensors and authors. |
415 |
+ |
416 |
+ All other non-permissive additional terms are considered "further |
417 |
+restrictions" within the meaning of section 10. If the Program as you |
418 |
+received it, or any part of it, contains a notice stating that it is |
419 |
+governed by this License along with a term that is a further |
420 |
+restriction, you may remove that term. If a license document contains |
421 |
+a further restriction but permits relicensing or conveying under this |
422 |
+License, you may add to a covered work material governed by the terms |
423 |
+of that license document, provided that the further restriction does |
424 |
+not survive such relicensing or conveying. |
425 |
+ |
426 |
+ If you add terms to a covered work in accord with this section, you |
427 |
+must place, in the relevant source files, a statement of the |
428 |
+additional terms that apply to those files, or a notice indicating |
429 |
+where to find the applicable terms. |
430 |
+ |
431 |
+ Additional terms, permissive or non-permissive, may be stated in the |
432 |
+form of a separately written license, or stated as exceptions; |
433 |
+the above requirements apply either way. |
434 |
+ |
435 |
+ 8. Termination. |
436 |
+ |
437 |
+ You may not propagate or modify a covered work except as expressly |
438 |
+provided under this License. Any attempt otherwise to propagate or |
439 |
+modify it is void, and will automatically terminate your rights under |
440 |
+this License (including any patent licenses granted under the third |
441 |
+paragraph of section 11). |
442 |
+ |
443 |
+ However, if you cease all violation of this License, then your |
444 |
+license from a particular copyright holder is reinstated (a) |
445 |
+provisionally, unless and until the copyright holder explicitly and |
446 |
+finally terminates your license, and (b) permanently, if the copyright |
447 |
+holder fails to notify you of the violation by some reasonable means |
448 |
+prior to 60 days after the cessation. |
449 |
+ |
450 |
+ Moreover, your license from a particular copyright holder is |
451 |
+reinstated permanently if the copyright holder notifies you of the |
452 |
+violation by some reasonable means, this is the first time you have |
453 |
+received notice of violation of this License (for any work) from that |
454 |
+copyright holder, and you cure the violation prior to 30 days after |
455 |
+your receipt of the notice. |
456 |
+ |
457 |
+ Termination of your rights under this section does not terminate the |
458 |
+licenses of parties who have received copies or rights from you under |
459 |
+this License. If your rights have been terminated and not permanently |
460 |
+reinstated, you do not qualify to receive new licenses for the same |
461 |
+material under section 10. |
462 |
+ |
463 |
+ 9. Acceptance Not Required for Having Copies. |
464 |
+ |
465 |
+ You are not required to accept this License in order to receive or |
466 |
+run a copy of the Program. Ancillary propagation of a covered work |
467 |
+occurring solely as a consequence of using peer-to-peer transmission |
468 |
+to receive a copy likewise does not require acceptance. However, |
469 |
+nothing other than this License grants you permission to propagate or |
470 |
+modify any covered work. These actions infringe copyright if you do |
471 |
+not accept this License. Therefore, by modifying or propagating a |
472 |
+covered work, you indicate your acceptance of this License to do so. |
473 |
+ |
474 |
+ 10. Automatic Licensing of Downstream Recipients. |
475 |
+ |
476 |
+ Each time you convey a covered work, the recipient automatically |
477 |
+receives a license from the original licensors, to run, modify and |
478 |
+propagate that work, subject to this License. You are not responsible |
479 |
+for enforcing compliance by third parties with this License. |
480 |
+ |
481 |
+ An "entity transaction" is a transaction transferring control of an |
482 |
+organization, or substantially all assets of one, or subdividing an |
483 |
+organization, or merging organizations. If propagation of a covered |
484 |
+work results from an entity transaction, each party to that |
485 |
+transaction who receives a copy of the work also receives whatever |
486 |
+licenses to the work the party's predecessor in interest had or could |
487 |
+give under the previous paragraph, plus a right to possession of the |
488 |
+Corresponding Source of the work from the predecessor in interest, if |
489 |
+the predecessor has it or can get it with reasonable efforts. |
490 |
+ |
491 |
+ You may not impose any further restrictions on the exercise of the |
492 |
+rights granted or affirmed under this License. For example, you may |
493 |
+not impose a license fee, royalty, or other charge for exercise of |
494 |
+rights granted under this License, and you may not initiate litigation |
495 |
+(including a cross-claim or counterclaim in a lawsuit) alleging that |
496 |
+any patent claim is infringed by making, using, selling, offering for |
497 |
+sale, or importing the Program or any portion of it. |
498 |
+ |
499 |
+ 11. Patents. |
500 |
+ |
501 |
+ A "contributor" is a copyright holder who authorizes use under this |
502 |
+License of the Program or a work on which the Program is based. The |
503 |
+work thus licensed is called the contributor's "contributor version". |
504 |
+ |
505 |
+ A contributor's "essential patent claims" are all patent claims |
506 |
+owned or controlled by the contributor, whether already acquired or |
507 |
+hereafter acquired, that would be infringed by some manner, permitted |
508 |
+by this License, of making, using, or selling its contributor version, |
509 |
+but do not include claims that would be infringed only as a |
510 |
+consequence of further modification of the contributor version. For |
511 |
+purposes of this definition, "control" includes the right to grant |
512 |
+patent sublicenses in a manner consistent with the requirements of |
513 |
+this License. |
514 |
+ |
515 |
+ Each contributor grants you a non-exclusive, worldwide, royalty-free |
516 |
+patent license under the contributor's essential patent claims, to |
517 |
+make, use, sell, offer for sale, import and otherwise run, modify and |
518 |
+propagate the contents of its contributor version. |
519 |
+ |
520 |
+ In the following three paragraphs, a "patent license" is any express |
521 |
+agreement or commitment, however denominated, not to enforce a patent |
522 |
+(such as an express permission to practice a patent or covenant not to |
523 |
+sue for patent infringement). To "grant" such a patent license to a |
524 |
+party means to make such an agreement or commitment not to enforce a |
525 |
+patent against the party. |
526 |
+ |
527 |
+ If you convey a covered work, knowingly relying on a patent license, |
528 |
+and the Corresponding Source of the work is not available for anyone |
529 |
+to copy, free of charge and under the terms of this License, through a |
530 |
+publicly available network server or other readily accessible means, |
531 |
+then you must either (1) cause the Corresponding Source to be so |
532 |
+available, or (2) arrange to deprive yourself of the benefit of the |
533 |
+patent license for this particular work, or (3) arrange, in a manner |
534 |
+consistent with the requirements of this License, to extend the patent |
535 |
+license to downstream recipients. "Knowingly relying" means you have |
536 |
+actual knowledge that, but for the patent license, your conveying the |
537 |
+covered work in a country, or your recipient's use of the covered work |
538 |
+in a country, would infringe one or more identifiable patents in that |
539 |
+country that you have reason to believe are valid. |
540 |
+ |
541 |
+ If, pursuant to or in connection with a single transaction or |
542 |
+arrangement, you convey, or propagate by procuring conveyance of, a |
543 |
+covered work, and grant a patent license to some of the parties |
544 |
+receiving the covered work authorizing them to use, propagate, modify |
545 |
+or convey a specific copy of the covered work, then the patent license |
546 |
+you grant is automatically extended to all recipients of the covered |
547 |
+work and works based on it. |
548 |
+ |
549 |
+ A patent license is "discriminatory" if it does not include within |
550 |
+the scope of its coverage, prohibits the exercise of, or is |
551 |
+conditioned on the non-exercise of one or more of the rights that are |
552 |
+specifically granted under this License. You may not convey a covered |
553 |
+work if you are a party to an arrangement with a third party that is |
554 |
+in the business of distributing software, under which you make payment |
555 |
+to the third party based on the extent of your activity of conveying |
556 |
+the work, and under which the third party grants, to any of the |
557 |
+parties who would receive the covered work from you, a discriminatory |
558 |
+patent license (a) in connection with copies of the covered work |
559 |
+conveyed by you (or copies made from those copies), or (b) primarily |
560 |
+for and in connection with specific products or compilations that |
561 |
+contain the covered work, unless you entered into that arrangement, |
562 |
+or that patent license was granted, prior to 28 March 2007. |
563 |
+ |
564 |
+ Nothing in this License shall be construed as excluding or limiting |
565 |
+any implied license or other defenses to infringement that may |
566 |
+otherwise be available to you under applicable patent law. |
567 |
+ |
568 |
+ 12. No Surrender of Others' Freedom. |
569 |
+ |
570 |
+ If conditions are imposed on you (whether by court order, agreement or |
571 |
+otherwise) that contradict the conditions of this License, they do not |
572 |
+excuse you from the conditions of this License. If you cannot convey a |
573 |
+covered work so as to satisfy simultaneously your obligations under this |
574 |
+License and any other pertinent obligations, then as a consequence you may |
575 |
+not convey it at all. For example, if you agree to terms that obligate you |
576 |
+to collect a royalty for further conveying from those to whom you convey |
577 |
+the Program, the only way you could satisfy both those terms and this |
578 |
+License would be to refrain entirely from conveying the Program. |
579 |
+ |
580 |
+ 13. Use with the GNU Affero General Public License. |
581 |
+ |
582 |
+ Notwithstanding any other provision of this License, you have |
583 |
+permission to link or combine any covered work with a work licensed |
584 |
+under version 3 of the GNU Affero General Public License into a single |
585 |
+combined work, and to convey the resulting work. The terms of this |
586 |
+License will continue to apply to the part which is the covered work, |
587 |
+but the special requirements of the GNU Affero General Public License, |
588 |
+section 13, concerning interaction through a network will apply to the |
589 |
+combination as such. |
590 |
+ |
591 |
+ 14. Revised Versions of this License. |
592 |
+ |
593 |
+ The Free Software Foundation may publish revised and/or new versions of |
594 |
+the GNU General Public License from time to time. Such new versions will |
595 |
+be similar in spirit to the present version, but may differ in detail to |
596 |
+address new problems or concerns. |
597 |
+ |
598 |
+ Each version is given a distinguishing version number. If the |
599 |
+Program specifies that a certain numbered version of the GNU General |
600 |
+Public License "or any later version" applies to it, you have the |
601 |
+option of following the terms and conditions either of that numbered |
602 |
+version or of any later version published by the Free Software |
603 |
+Foundation. If the Program does not specify a version number of the |
604 |
+GNU General Public License, you may choose any version ever published |
605 |
+by the Free Software Foundation. |
606 |
+ |
607 |
+ If the Program specifies that a proxy can decide which future |
608 |
+versions of the GNU General Public License can be used, that proxy's |
609 |
+public statement of acceptance of a version permanently authorizes you |
610 |
+to choose that version for the Program. |
611 |
+ |
612 |
+ Later license versions may give you additional or different |
613 |
+permissions. However, no additional obligations are imposed on any |
614 |
+author or copyright holder as a result of your choosing to follow a |
615 |
+later version. |
616 |
+ |
617 |
+ 15. Disclaimer of Warranty. |
618 |
+ |
619 |
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY |
620 |
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT |
621 |
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY |
622 |
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, |
623 |
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR |
624 |
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM |
625 |
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF |
626 |
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION. |
627 |
+ |
628 |
+ 16. Limitation of Liability. |
629 |
+ |
630 |
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING |
631 |
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS |
632 |
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY |
633 |
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE |
634 |
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF |
635 |
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD |
636 |
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), |
637 |
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF |
638 |
+SUCH DAMAGES. |
639 |
+ |
640 |
+ 17. Interpretation of Sections 15 and 16. |
641 |
+ |
642 |
+ If the disclaimer of warranty and limitation of liability provided |
643 |
+above cannot be given local legal effect according to their terms, |
644 |
+reviewing courts shall apply local law that most closely approximates |
645 |
+an absolute waiver of all civil liability in connection with the |
646 |
+Program, unless a warranty or assumption of liability accompanies a |
647 |
+copy of the Program in return for a fee. |
648 |
+ |
649 |
+ END OF TERMS AND CONDITIONS |
650 |
+ |
651 |
+ How to Apply These Terms to Your New Programs |
652 |
+ |
653 |
+ If you develop a new program, and you want it to be of the greatest |
654 |
+possible use to the public, the best way to achieve this is to make it |
655 |
+free software which everyone can redistribute and change under these terms. |
656 |
+ |
657 |
+ To do so, attach the following notices to the program. It is safest |
658 |
+to attach them to the start of each source file to most effectively |
659 |
+state the exclusion of warranty; and each file should have at least |
660 |
+the "copyright" line and a pointer to where the full notice is found. |
661 |
+ |
662 |
+ <one line to give the program's name and a brief idea of what it does.> |
663 |
+ Copyright (C) <year> <name of author> |
664 |
+ |
665 |
+ This program is free software: you can redistribute it and/or modify |
666 |
+ it under the terms of the GNU General Public License as published by |
667 |
+ the Free Software Foundation, either version 3 of the License, or |
668 |
+ (at your option) any later version. |
669 |
+ |
670 |
+ This program is distributed in the hope that it will be useful, |
671 |
+ but WITHOUT ANY WARRANTY; without even the implied warranty of |
672 |
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
673 |
+ GNU General Public License for more details. |
674 |
+ |
675 |
+ You should have received a copy of the GNU General Public License |
676 |
+ along with this program. If not, see <http://www.gnu.org/licenses/>. |
677 |
+ |
678 |
+Also add information on how to contact you by electronic and paper mail. |
679 |
+ |
680 |
+ If the program does terminal interaction, make it output a short |
681 |
+notice like this when it starts in an interactive mode: |
682 |
+ |
683 |
+ <program> Copyright (C) <year> <name of author> |
684 |
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. |
685 |
+ This is free software, and you are welcome to redistribute it |
686 |
+ under certain conditions; type `show c' for details. |
687 |
+ |
688 |
+The hypothetical commands `show w' and `show c' should show the appropriate |
689 |
+parts of the General Public License. Of course, your program's commands |
690 |
+might be different; for a GUI interface, you would use an "about box". |
691 |
+ |
692 |
+ You should also get your employer (if you work as a programmer) or school, |
693 |
+if any, to sign a "copyright disclaimer" for the program, if necessary. |
694 |
+For more information on this, and how to apply and follow the GNU GPL, see |
695 |
+<http://www.gnu.org/licenses/>. |
696 |
+ |
697 |
+ The GNU General Public License does not permit incorporating your program |
698 |
+into proprietary programs. If your program is a subroutine library, you |
699 |
+may consider it more useful to permit linking proprietary applications with |
700 |
+the library. If this is what you want to do, use the GNU Lesser General |
701 |
+Public License instead of this License. But first, please read |
702 |
+<http://www.gnu.org/philosophy/why-not-lgpl.html>. |
703 |
|
704 |
diff --git a/misc/test-revdep-pax/INSTALL b/misc/test-revdep-pax/INSTALL |
705 |
new file mode 100644 |
706 |
index 0000000..7d1c323 |
707 |
--- /dev/null |
708 |
+++ b/misc/test-revdep-pax/INSTALL |
709 |
@@ -0,0 +1,365 @@ |
710 |
+Installation Instructions |
711 |
+************************* |
712 |
+ |
713 |
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, |
714 |
+2006, 2007, 2008, 2009 Free Software Foundation, Inc. |
715 |
+ |
716 |
+ Copying and distribution of this file, with or without modification, |
717 |
+are permitted in any medium without royalty provided the copyright |
718 |
+notice and this notice are preserved. This file is offered as-is, |
719 |
+without warranty of any kind. |
720 |
+ |
721 |
+Basic Installation |
722 |
+================== |
723 |
+ |
724 |
+ Briefly, the shell commands `./configure; make; make install' should |
725 |
+configure, build, and install this package. The following |
726 |
+more-detailed instructions are generic; see the `README' file for |
727 |
+instructions specific to this package. Some packages provide this |
728 |
+`INSTALL' file but do not implement all of the features documented |
729 |
+below. The lack of an optional feature in a given package is not |
730 |
+necessarily a bug. More recommendations for GNU packages can be found |
731 |
+in *note Makefile Conventions: (standards)Makefile Conventions. |
732 |
+ |
733 |
+ The `configure' shell script attempts to guess correct values for |
734 |
+various system-dependent variables used during compilation. It uses |
735 |
+those values to create a `Makefile' in each directory of the package. |
736 |
+It may also create one or more `.h' files containing system-dependent |
737 |
+definitions. Finally, it creates a shell script `config.status' that |
738 |
+you can run in the future to recreate the current configuration, and a |
739 |
+file `config.log' containing compiler output (useful mainly for |
740 |
+debugging `configure'). |
741 |
+ |
742 |
+ It can also use an optional file (typically called `config.cache' |
743 |
+and enabled with `--cache-file=config.cache' or simply `-C') that saves |
744 |
+the results of its tests to speed up reconfiguring. Caching is |
745 |
+disabled by default to prevent problems with accidental use of stale |
746 |
+cache files. |
747 |
+ |
748 |
+ If you need to do unusual things to compile the package, please try |
749 |
+to figure out how `configure' could check whether to do them, and mail |
750 |
+diffs or instructions to the address given in the `README' so they can |
751 |
+be considered for the next release. If you are using the cache, and at |
752 |
+some point `config.cache' contains results you don't want to keep, you |
753 |
+may remove or edit it. |
754 |
+ |
755 |
+ The file `configure.ac' (or `configure.in') is used to create |
756 |
+`configure' by a program called `autoconf'. You need `configure.ac' if |
757 |
+you want to change it or regenerate `configure' using a newer version |
758 |
+of `autoconf'. |
759 |
+ |
760 |
+ The simplest way to compile this package is: |
761 |
+ |
762 |
+ 1. `cd' to the directory containing the package's source code and type |
763 |
+ `./configure' to configure the package for your system. |
764 |
+ |
765 |
+ Running `configure' might take a while. While running, it prints |
766 |
+ some messages telling which features it is checking for. |
767 |
+ |
768 |
+ 2. Type `make' to compile the package. |
769 |
+ |
770 |
+ 3. Optionally, type `make check' to run any self-tests that come with |
771 |
+ the package, generally using the just-built uninstalled binaries. |
772 |
+ |
773 |
+ 4. Type `make install' to install the programs and any data files and |
774 |
+ documentation. When installing into a prefix owned by root, it is |
775 |
+ recommended that the package be configured and built as a regular |
776 |
+ user, and only the `make install' phase executed with root |
777 |
+ privileges. |
778 |
+ |
779 |
+ 5. Optionally, type `make installcheck' to repeat any self-tests, but |
780 |
+ this time using the binaries in their final installed location. |
781 |
+ This target does not install anything. Running this target as a |
782 |
+ regular user, particularly if the prior `make install' required |
783 |
+ root privileges, verifies that the installation completed |
784 |
+ correctly. |
785 |
+ |
786 |
+ 6. You can remove the program binaries and object files from the |
787 |
+ source code directory by typing `make clean'. To also remove the |
788 |
+ files that `configure' created (so you can compile the package for |
789 |
+ a different kind of computer), type `make distclean'. There is |
790 |
+ also a `make maintainer-clean' target, but that is intended mainly |
791 |
+ for the package's developers. If you use it, you may have to get |
792 |
+ all sorts of other programs in order to regenerate files that came |
793 |
+ with the distribution. |
794 |
+ |
795 |
+ 7. Often, you can also type `make uninstall' to remove the installed |
796 |
+ files again. In practice, not all packages have tested that |
797 |
+ uninstallation works correctly, even though it is required by the |
798 |
+ GNU Coding Standards. |
799 |
+ |
800 |
+ 8. Some packages, particularly those that use Automake, provide `make |
801 |
+ distcheck', which can by used by developers to test that all other |
802 |
+ targets like `make install' and `make uninstall' work correctly. |
803 |
+ This target is generally not run by end users. |
804 |
+ |
805 |
+Compilers and Options |
806 |
+===================== |
807 |
+ |
808 |
+ Some systems require unusual options for compilation or linking that |
809 |
+the `configure' script does not know about. Run `./configure --help' |
810 |
+for details on some of the pertinent environment variables. |
811 |
+ |
812 |
+ You can give `configure' initial values for configuration parameters |
813 |
+by setting variables in the command line or in the environment. Here |
814 |
+is an example: |
815 |
+ |
816 |
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix |
817 |
+ |
818 |
+ *Note Defining Variables::, for more details. |
819 |
+ |
820 |
+Compiling For Multiple Architectures |
821 |
+==================================== |
822 |
+ |
823 |
+ You can compile the package for more than one kind of computer at the |
824 |
+same time, by placing the object files for each architecture in their |
825 |
+own directory. To do this, you can use GNU `make'. `cd' to the |
826 |
+directory where you want the object files and executables to go and run |
827 |
+the `configure' script. `configure' automatically checks for the |
828 |
+source code in the directory that `configure' is in and in `..'. This |
829 |
+is known as a "VPATH" build. |
830 |
+ |
831 |
+ With a non-GNU `make', it is safer to compile the package for one |
832 |
+architecture at a time in the source code directory. After you have |
833 |
+installed the package for one architecture, use `make distclean' before |
834 |
+reconfiguring for another architecture. |
835 |
+ |
836 |
+ On MacOS X 10.5 and later systems, you can create libraries and |
837 |
+executables that work on multiple system types--known as "fat" or |
838 |
+"universal" binaries--by specifying multiple `-arch' options to the |
839 |
+compiler but only a single `-arch' option to the preprocessor. Like |
840 |
+this: |
841 |
+ |
842 |
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ |
843 |
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ |
844 |
+ CPP="gcc -E" CXXCPP="g++ -E" |
845 |
+ |
846 |
+ This is not guaranteed to produce working output in all cases, you |
847 |
+may have to build one architecture at a time and combine the results |
848 |
+using the `lipo' tool if you have problems. |
849 |
+ |
850 |
+Installation Names |
851 |
+================== |
852 |
+ |
853 |
+ By default, `make install' installs the package's commands under |
854 |
+`/usr/local/bin', include files under `/usr/local/include', etc. You |
855 |
+can specify an installation prefix other than `/usr/local' by giving |
856 |
+`configure' the option `--prefix=PREFIX', where PREFIX must be an |
857 |
+absolute file name. |
858 |
+ |
859 |
+ You can specify separate installation prefixes for |
860 |
+architecture-specific files and architecture-independent files. If you |
861 |
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses |
862 |
+PREFIX as the prefix for installing programs and libraries. |
863 |
+Documentation and other data files still use the regular prefix. |
864 |
+ |
865 |
+ In addition, if you use an unusual directory layout you can give |
866 |
+options like `--bindir=DIR' to specify different values for particular |
867 |
+kinds of files. Run `configure --help' for a list of the directories |
868 |
+you can set and what kinds of files go in them. In general, the |
869 |
+default for these options is expressed in terms of `${prefix}', so that |
870 |
+specifying just `--prefix' will affect all of the other directory |
871 |
+specifications that were not explicitly provided. |
872 |
+ |
873 |
+ The most portable way to affect installation locations is to pass the |
874 |
+correct locations to `configure'; however, many packages provide one or |
875 |
+both of the following shortcuts of passing variable assignments to the |
876 |
+`make install' command line to change installation locations without |
877 |
+having to reconfigure or recompile. |
878 |
+ |
879 |
+ The first method involves providing an override variable for each |
880 |
+affected directory. For example, `make install |
881 |
+prefix=/alternate/directory' will choose an alternate location for all |
882 |
+directory configuration variables that were expressed in terms of |
883 |
+`${prefix}'. Any directories that were specified during `configure', |
884 |
+but not in terms of `${prefix}', must each be overridden at install |
885 |
+time for the entire installation to be relocated. The approach of |
886 |
+makefile variable overrides for each directory variable is required by |
887 |
+the GNU Coding Standards, and ideally causes no recompilation. |
888 |
+However, some platforms have known limitations with the semantics of |
889 |
+shared libraries that end up requiring recompilation when using this |
890 |
+method, particularly noticeable in packages that use GNU Libtool. |
891 |
+ |
892 |
+ The second method involves providing the `DESTDIR' variable. For |
893 |
+example, `make install DESTDIR=/alternate/directory' will prepend |
894 |
+`/alternate/directory' before all installation names. The approach of |
895 |
+`DESTDIR' overrides is not required by the GNU Coding Standards, and |
896 |
+does not work on platforms that have drive letters. On the other hand, |
897 |
+it does better at avoiding recompilation issues, and works well even |
898 |
+when some directory options were not specified in terms of `${prefix}' |
899 |
+at `configure' time. |
900 |
+ |
901 |
+Optional Features |
902 |
+================= |
903 |
+ |
904 |
+ If the package supports it, you can cause programs to be installed |
905 |
+with an extra prefix or suffix on their names by giving `configure' the |
906 |
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. |
907 |
+ |
908 |
+ Some packages pay attention to `--enable-FEATURE' options to |
909 |
+`configure', where FEATURE indicates an optional part of the package. |
910 |
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE |
911 |
+is something like `gnu-as' or `x' (for the X Window System). The |
912 |
+`README' should mention any `--enable-' and `--with-' options that the |
913 |
+package recognizes. |
914 |
+ |
915 |
+ For packages that use the X Window System, `configure' can usually |
916 |
+find the X include and library files automatically, but if it doesn't, |
917 |
+you can use the `configure' options `--x-includes=DIR' and |
918 |
+`--x-libraries=DIR' to specify their locations. |
919 |
+ |
920 |
+ Some packages offer the ability to configure how verbose the |
921 |
+execution of `make' will be. For these packages, running `./configure |
922 |
+--enable-silent-rules' sets the default to minimal output, which can be |
923 |
+overridden with `make V=1'; while running `./configure |
924 |
+--disable-silent-rules' sets the default to verbose, which can be |
925 |
+overridden with `make V=0'. |
926 |
+ |
927 |
+Particular systems |
928 |
+================== |
929 |
+ |
930 |
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU |
931 |
+CC is not installed, it is recommended to use the following options in |
932 |
+order to use an ANSI C compiler: |
933 |
+ |
934 |
+ ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" |
935 |
+ |
936 |
+and if that doesn't work, install pre-built binaries of GCC for HP-UX. |
937 |
+ |
938 |
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot |
939 |
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as |
940 |
+a workaround. If GNU CC is not installed, it is therefore recommended |
941 |
+to try |
942 |
+ |
943 |
+ ./configure CC="cc" |
944 |
+ |
945 |
+and if that doesn't work, try |
946 |
+ |
947 |
+ ./configure CC="cc -nodtk" |
948 |
+ |
949 |
+ On Solaris, don't put `/usr/ucb' early in your `PATH'. This |
950 |
+directory contains several dysfunctional programs; working variants of |
951 |
+these programs are available in `/usr/bin'. So, if you need `/usr/ucb' |
952 |
+in your `PATH', put it _after_ `/usr/bin'. |
953 |
+ |
954 |
+ On Haiku, software installed for all users goes in `/boot/common', |
955 |
+not `/usr/local'. It is recommended to use the following options: |
956 |
+ |
957 |
+ ./configure --prefix=/boot/common |
958 |
+ |
959 |
+Specifying the System Type |
960 |
+========================== |
961 |
+ |
962 |
+ There may be some features `configure' cannot figure out |
963 |
+automatically, but needs to determine by the type of machine the package |
964 |
+will run on. Usually, assuming the package is built to be run on the |
965 |
+_same_ architectures, `configure' can figure that out, but if it prints |
966 |
+a message saying it cannot guess the machine type, give it the |
967 |
+`--build=TYPE' option. TYPE can either be a short name for the system |
968 |
+type, such as `sun4', or a canonical name which has the form: |
969 |
+ |
970 |
+ CPU-COMPANY-SYSTEM |
971 |
+ |
972 |
+where SYSTEM can have one of these forms: |
973 |
+ |
974 |
+ OS |
975 |
+ KERNEL-OS |
976 |
+ |
977 |
+ See the file `config.sub' for the possible values of each field. If |
978 |
+`config.sub' isn't included in this package, then this package doesn't |
979 |
+need to know the machine type. |
980 |
+ |
981 |
+ If you are _building_ compiler tools for cross-compiling, you should |
982 |
+use the option `--target=TYPE' to select the type of system they will |
983 |
+produce code for. |
984 |
+ |
985 |
+ If you want to _use_ a cross compiler, that generates code for a |
986 |
+platform different from the build platform, you should specify the |
987 |
+"host" platform (i.e., that on which the generated programs will |
988 |
+eventually be run) with `--host=TYPE'. |
989 |
+ |
990 |
+Sharing Defaults |
991 |
+================ |
992 |
+ |
993 |
+ If you want to set default values for `configure' scripts to share, |
994 |
+you can create a site shell script called `config.site' that gives |
995 |
+default values for variables like `CC', `cache_file', and `prefix'. |
996 |
+`configure' looks for `PREFIX/share/config.site' if it exists, then |
997 |
+`PREFIX/etc/config.site' if it exists. Or, you can set the |
998 |
+`CONFIG_SITE' environment variable to the location of the site script. |
999 |
+A warning: not all `configure' scripts look for a site script. |
1000 |
+ |
1001 |
+Defining Variables |
1002 |
+================== |
1003 |
+ |
1004 |
+ Variables not defined in a site shell script can be set in the |
1005 |
+environment passed to `configure'. However, some packages may run |
1006 |
+configure again during the build, and the customized values of these |
1007 |
+variables may be lost. In order to avoid this problem, you should set |
1008 |
+them in the `configure' command line, using `VAR=value'. For example: |
1009 |
+ |
1010 |
+ ./configure CC=/usr/local2/bin/gcc |
1011 |
+ |
1012 |
+causes the specified `gcc' to be used as the C compiler (unless it is |
1013 |
+overridden in the site shell script). |
1014 |
+ |
1015 |
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to |
1016 |
+an Autoconf bug. Until the bug is fixed you can use this workaround: |
1017 |
+ |
1018 |
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash |
1019 |
+ |
1020 |
+`configure' Invocation |
1021 |
+====================== |
1022 |
+ |
1023 |
+ `configure' recognizes the following options to control how it |
1024 |
+operates. |
1025 |
+ |
1026 |
+`--help' |
1027 |
+`-h' |
1028 |
+ Print a summary of all of the options to `configure', and exit. |
1029 |
+ |
1030 |
+`--help=short' |
1031 |
+`--help=recursive' |
1032 |
+ Print a summary of the options unique to this package's |
1033 |
+ `configure', and exit. The `short' variant lists options used |
1034 |
+ only in the top level, while the `recursive' variant lists options |
1035 |
+ also present in any nested packages. |
1036 |
+ |
1037 |
+`--version' |
1038 |
+`-V' |
1039 |
+ Print the version of Autoconf used to generate the `configure' |
1040 |
+ script, and exit. |
1041 |
+ |
1042 |
+`--cache-file=FILE' |
1043 |
+ Enable the cache: use and save the results of the tests in FILE, |
1044 |
+ traditionally `config.cache'. FILE defaults to `/dev/null' to |
1045 |
+ disable caching. |
1046 |
+ |
1047 |
+`--config-cache' |
1048 |
+`-C' |
1049 |
+ Alias for `--cache-file=config.cache'. |
1050 |
+ |
1051 |
+`--quiet' |
1052 |
+`--silent' |
1053 |
+`-q' |
1054 |
+ Do not print messages saying which checks are being made. To |
1055 |
+ suppress all normal output, redirect it to `/dev/null' (any error |
1056 |
+ messages will still be shown). |
1057 |
+ |
1058 |
+`--srcdir=DIR' |
1059 |
+ Look for the package's source code in directory DIR. Usually |
1060 |
+ `configure' can determine that directory automatically. |
1061 |
+ |
1062 |
+`--prefix=DIR' |
1063 |
+ Use DIR as the installation prefix. *note Installation Names:: |
1064 |
+ for more details, including other options available for fine-tuning |
1065 |
+ the installation locations. |
1066 |
+ |
1067 |
+`--no-create' |
1068 |
+`-n' |
1069 |
+ Run the configure checks, but stop before creating any output |
1070 |
+ files. |
1071 |
+ |
1072 |
+`configure' also accepts some other, not widely useful, options. Run |
1073 |
+`configure --help' for more details. |
1074 |
+ |
1075 |
|
1076 |
diff --git a/misc/test-revdep-pax/Makefile.am b/misc/test-revdep-pax/Makefile.am |
1077 |
new file mode 100644 |
1078 |
index 0000000..d29bd12 |
1079 |
--- /dev/null |
1080 |
+++ b/misc/test-revdep-pax/Makefile.am |
1081 |
@@ -0,0 +1,10 @@ |
1082 |
+ACLOCAL_AMFLAGS = -I m4 |
1083 |
+ |
1084 |
+bin_PROGRAMS = testrevdeppax |
1085 |
+testrevdeppax_SOURCES = testrevdeppax.c |
1086 |
+testrevdeppax_LDADD = libmyrevdeppax.la |
1087 |
+ |
1088 |
+lib_LTLIBRARIES = libmyrevdeppax.la |
1089 |
+libmyrevdeppax_la_SOURCES = libmyrevdeppax.c |
1090 |
+ |
1091 |
+bin_SCRIPTS = testrevdeppax.sh |
1092 |
|
1093 |
diff --git a/misc/test-revdep-pax/README b/misc/test-revdep-pax/README |
1094 |
new file mode 100644 |
1095 |
index 0000000..83af910 |
1096 |
--- /dev/null |
1097 |
+++ b/misc/test-revdep-pax/README |
1098 |
@@ -0,0 +1,35 @@ |
1099 |
+ |
1100 |
+This POC is based on paxmark-libs and is used to test revdep-pax. |
1101 |
+ |
1102 |
+Because revdep-pax only works on packages already installed on the |
1103 |
+system, we can't build in a test triggered by USE="test" unless we first |
1104 |
+RDEPEND on this package. But this would mean putting a garbate package |
1105 |
+just for a test and we don't want to polute people's systems. |
1106 |
+ |
1107 |
+So here's how you test revdep-pax with this package. |
1108 |
+ |
1109 |
+EITHER prepare the package yourself: |
1110 |
+ |
1111 |
+ 1. ./autogen.sh |
1112 |
+ 2. ./configure |
1113 |
+ 3. make dist |
1114 |
+ 4. cp testrevdeppax-0.1.tar.gz /usr/portage/distfiles/ |
1115 |
+ 5. cp testrevdeppax-0.1.ebuild /some/overlay/location |
1116 |
+ 6. repoman manifest |
1117 |
+ |
1118 |
+ |
1119 |
+OR use my overlay |
1120 |
+ |
1121 |
+ 1. layman -a blueness |
1122 |
+ 2. echo "source /var/lib/layman/make.conf" >> /etc/make.conf |
1123 |
+ |
1124 |
+ |
1125 |
+THEN |
1126 |
+ |
1127 |
+ 1. ACCEPT_KEYWORDS="~amd64" emerge testrevdeppax |
1128 |
+ 2. testrevdeppax.sh |
1129 |
+ |
1130 |
+The script tests all possible combinations of the RANDMMAP flag on both |
1131 |
+the binary /usr/bin/testrevdeppax and library /usr/lib64/libmyrevdeppax.so.0.0.0 |
1132 |
+It then tests both forward migrating the pax markings from the binary to the |
1133 |
+library and then reverse migrating them from the library to the binary. |
1134 |
|
1135 |
diff --git a/misc/test-revdep-pax/autogen.sh b/misc/test-revdep-pax/autogen.sh |
1136 |
new file mode 100755 |
1137 |
index 0000000..917d1a7 |
1138 |
--- /dev/null |
1139 |
+++ b/misc/test-revdep-pax/autogen.sh |
1140 |
@@ -0,0 +1,7 @@ |
1141 |
+#!/bin/sh |
1142 |
+ |
1143 |
+aclocal && \ |
1144 |
+autoheader && \ |
1145 |
+autoconf && \ |
1146 |
+libtoolize --copy && \ |
1147 |
+automake --add-missing --copy |
1148 |
|
1149 |
diff --git a/misc/test-revdep-pax/configure.ac b/misc/test-revdep-pax/configure.ac |
1150 |
new file mode 100644 |
1151 |
index 0000000..d970185 |
1152 |
--- /dev/null |
1153 |
+++ b/misc/test-revdep-pax/configure.ac |
1154 |
@@ -0,0 +1,18 @@ |
1155 |
+AC_PREREQ([2.68]) |
1156 |
+AC_INIT([testrevdeppax],[0.1]) |
1157 |
+AC_CONFIG_SRCDIR([libmyrevdeppax.c]) |
1158 |
+AC_CONFIG_HEADERS([config.h]) |
1159 |
+ |
1160 |
+AM_INIT_AUTOMAKE([1.11 foreign]) |
1161 |
+AM_SILENT_RULES([yes]) |
1162 |
+ |
1163 |
+LT_PREREQ([2.4]) |
1164 |
+LT_INIT([dlopen]) |
1165 |
+AC_CONFIG_MACRO_DIR([m4]) |
1166 |
+ |
1167 |
+AC_PROG_CC |
1168 |
+ |
1169 |
+AC_CHECK_LIB([myrevdeppax], [main]) |
1170 |
+ |
1171 |
+AC_CONFIG_FILES([Makefile]) |
1172 |
+AC_OUTPUT |
1173 |
|
1174 |
diff --git a/misc/test-revdep-pax/libmyrevdeppax.c b/misc/test-revdep-pax/libmyrevdeppax.c |
1175 |
new file mode 100644 |
1176 |
index 0000000..6706b30 |
1177 |
--- /dev/null |
1178 |
+++ b/misc/test-revdep-pax/libmyrevdeppax.c |
1179 |
@@ -0,0 +1,5 @@ |
1180 |
+void |
1181 |
+doit() { |
1182 |
+ ; |
1183 |
+ return ; |
1184 |
+} |
1185 |
|
1186 |
diff --git a/misc/test-revdep-pax/testrevdeppax-0.1.ebuild b/misc/test-revdep-pax/testrevdeppax-0.1.ebuild |
1187 |
new file mode 100644 |
1188 |
index 0000000..70e3523 |
1189 |
--- /dev/null |
1190 |
+++ b/misc/test-revdep-pax/testrevdeppax-0.1.ebuild |
1191 |
@@ -0,0 +1,17 @@ |
1192 |
+# Copyright 1999-2011 Gentoo Foundation |
1193 |
+# Distributed under the terms of the GNU General Public License v2 |
1194 |
+# $Header: $ |
1195 |
+ |
1196 |
+EAPI="4" |
1197 |
+ |
1198 |
+DESCRIPTION="This is a garbage package to be abused by revdep-pax" |
1199 |
+HOMEPAGE="http://dev.gentoo.org/~blueness/elfix" |
1200 |
+SRC_URI="http://dev.gentoo.org/~blueness/elfix/${P}.tar.gz" |
1201 |
+ |
1202 |
+LICENSE="GPL-3" |
1203 |
+SLOT="0" |
1204 |
+KEYWORDS="~amd64 ~x86" |
1205 |
+IUSE="" |
1206 |
+ |
1207 |
+DEPEND="" |
1208 |
+RDEPEND="${DEPEND}" |
1209 |
|
1210 |
diff --git a/misc/test-revdep-pax/testrevdeppax.c b/misc/test-revdep-pax/testrevdeppax.c |
1211 |
new file mode 100644 |
1212 |
index 0000000..4ace814 |
1213 |
--- /dev/null |
1214 |
+++ b/misc/test-revdep-pax/testrevdeppax.c |
1215 |
@@ -0,0 +1,5 @@ |
1216 |
+int |
1217 |
+main() { |
1218 |
+ doit(); |
1219 |
+ return 0; |
1220 |
+} |
1221 |
|
1222 |
diff --git a/misc/test-revdep-pax/testrevdeppax.sh b/misc/test-revdep-pax/testrevdeppax.sh |
1223 |
new file mode 100644 |
1224 |
index 0000000..60a97d7 |
1225 |
--- /dev/null |
1226 |
+++ b/misc/test-revdep-pax/testrevdeppax.sh |
1227 |
@@ -0,0 +1,3 @@ |
1228 |
+#!/bin/bash |
1229 |
+ |
1230 |
+echo "stub" |