Module Name: src Committed By: christos Date: Thu Mar 8 20:30:38 UTC 2012
Added Files: src/external/gpl2/xcvs/dist/acl: COPYING COPYING.LIB INSTALL README aclconfig.default Log Message: add acl info To generate a diff of this commit: cvs rdiff -u -r0 -r1.1 src/external/gpl2/xcvs/dist/acl/COPYING \ src/external/gpl2/xcvs/dist/acl/COPYING.LIB \ src/external/gpl2/xcvs/dist/acl/INSTALL \ src/external/gpl2/xcvs/dist/acl/README \ src/external/gpl2/xcvs/dist/acl/aclconfig.default Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files.
Added files: Index: src/external/gpl2/xcvs/dist/acl/COPYING diff -u /dev/null src/external/gpl2/xcvs/dist/acl/COPYING:1.1 --- /dev/null Thu Mar 8 15:30:39 2012 +++ src/external/gpl2/xcvs/dist/acl/COPYING Thu Mar 8 15:30:38 2012 @@ -0,0 +1,248 @@ + + GNU GENERAL PUBLIC LICENSE + Version 1, February 1989 + + Copyright (C) 1989 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The license agreements of most software companies try to keep users +at the mercy of those companies. By contrast, our General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. The +General Public License applies to the Free Software Foundation's +software and to any other program whose authors commit to using it. +You can use it for your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Specifically, the General Public License is designed to make +sure that you have the freedom to give away or sell copies of free +software, that you receive source code or can get it if you want it, +that you can change the software or use pieces of it in new free +programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of a such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must tell them their rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any program or other work which +contains a notice placed by the copyright holder saying it may be +distributed under the terms of this General Public License. The +"Program", below, refers to any such program or work, and a "work based +on the Program" means either the Program or any work containing the +Program or a portion of it, either verbatim or with modifications. Each +licensee is addressed as "you". + + 1. You may copy and distribute verbatim copies of the Program's source +code as you receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice and +disclaimer of warranty; keep intact all the notices that refer to this +General Public License and to the absence of any warranty; and give any +other recipients of the Program a copy of this General Public License +along with the Program. You may charge a fee for the physical act of +transferring a copy. + + 2. You may modify your copy or copies of the Program or any portion of +it, and copy and distribute such modifications under the terms of Paragraph +1 above, provided that you also do the following: + + a) cause the modified files to carry prominent notices stating that + you changed the files and the date of any change; and + + b) cause the whole of any work that you distribute or publish, that + in whole or in part contains the Program or any part thereof, either + with or without modifications, to be licensed at no charge to all + third parties under the terms of this General Public License (except + that you may choose to grant warranty protection to some or all + third parties, at your option). + + c) If the modified program normally reads commands interactively when + run, you must cause it, when started running for such interactive use + in the simplest and most usual way, to print or display an + announcement including an appropriate copyright notice and a notice + that there is no warranty (or else, saying that you provide a + warranty) and that users may redistribute the program under these + conditions, and telling the user how to view a copy of this General + Public License. + + d) You may charge a fee for the physical act of transferring a + copy, and you may at your option offer warranty protection in + exchange for a fee. + +Mere aggregation of another independent work with the Program (or its +derivative) on a volume of a storage or distribution medium does not bring +the other work under the scope of these terms. + + 3. You may copy and distribute the Program (or a portion or derivative of +it, under Paragraph 2) in object code or executable form under the terms of +Paragraphs 1 and 2 above provided that you also do one of the following: + + a) accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of + Paragraphs 1 and 2 above; or, + + b) accompany it with a written offer, valid for at least three + years, to give any third party free (except for a nominal charge + for the cost of distribution) a complete machine-readable copy of the + corresponding source code, to be distributed under the terms of + Paragraphs 1 and 2 above; or, + + c) accompany it with the information you received as to where the + corresponding source code may be obtained. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form alone.) + +Source code for a work means the preferred form of the work for making +modifications to it. For an executable file, complete source code means +all the source code for all modules it contains; but, as a special +exception, it need not include source code for modules which are standard +libraries that accompany the operating system on which the executable +file runs, or for standard header files or definitions files that +accompany that operating system. + + 4. You may not copy, modify, sublicense, distribute or transfer the +Program except as expressly provided under this General Public License. +Any attempt otherwise to copy, modify, sublicense, distribute or transfer +the Program is void, and will automatically terminate your rights to use +the Program under this License. However, parties who have received +copies, or rights to use copies, from you under this General Public +License will not have their licenses terminated so long as such parties +remain in full compliance. + + 5. By copying, distributing or modifying the Program (or any work based +on the Program) you indicate your acceptance of this license to do so, +and all its terms and conditions. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the original +licensor to copy, distribute or modify the Program subject to these +terms and conditions. You may not impose any further restrictions on the +recipients' exercise of the rights granted herein. + + 7. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of the license which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +the license, you may choose any version ever published by the Free Software +Foundation. + + 8. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to humanity, the best way to achieve this is to make it +free software which everyone can redistribute and change under these +terms. + + To do so, attach the following notices to the program. It is safest to +attach them to the start of each source file to most effectively convey +the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) 19yy <name of author> + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 1, or (at your option) + any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19xx name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the +appropriate parts of the General Public License. Of course, the +commands you use may be called something other than `show w' and `show +c'; they could even be mouse-clicks or menu items--whatever suits your +program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + program `Gnomovision' (a program to direct compilers to make passes + at assemblers) written by James Hacker. + + <signature of Ty Coon>, 1 April 1989 + Ty Coon, President of Vice + +That's all there is to it! Index: src/external/gpl2/xcvs/dist/acl/COPYING.LIB diff -u /dev/null src/external/gpl2/xcvs/dist/acl/COPYING.LIB:1.1 --- /dev/null Thu Mar 8 15:30:39 2012 +++ src/external/gpl2/xcvs/dist/acl/COPYING.LIB Thu Mar 8 15:30:38 2012 @@ -0,0 +1,481 @@ + + GNU LIBRARY GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1991 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the library GPL. It is + numbered 2 because it goes with version 2 of the ordinary GPL.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Library General Public License, applies to some +specially designated Free Software Foundation software, and to any +other libraries whose authors decide to use it. You can use it for +your libraries, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if +you distribute copies of the library, or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link a program with the library, you must provide +complete object files to the recipients so that they can relink them +with the library, after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + Our method of protecting your rights has two steps: (1) copyright +the library, and (2) offer you this license which gives you legal +permission to copy, distribute and/or modify the library. + + Also, for each distributor's protection, we want to make certain +that everyone understands that there is no warranty for this free +library. If the library is modified by someone else and passed on, we +want its recipients to know that what they have is not the original +version, so that any problems introduced by others will not reflect on +the original authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that companies distributing free +software will individually obtain patent licenses, thus in effect +transforming the program into proprietary software. To prevent this, +we have made it clear that any patent must be licensed for everyone's +free use or not licensed at all. + + Most GNU software, including some libraries, is covered by the ordinary +GNU General Public License, which was designed for utility programs. This +license, the GNU Library General Public License, applies to certain +designated libraries. This license is quite different from the ordinary +one; be sure to read it in full, and don't assume that anything in it is +the same as in the ordinary license. + + The reason we have a separate public license for some libraries is that +they blur the distinction we usually make between modifying or adding to a +program and simply using it. Linking a program with a library, without +changing the library, is in some sense simply using the library, and is +analogous to running a utility program or application program. However, in +a textual and legal sense, the linked executable is a combined work, a +derivative of the original library, and the ordinary General Public License +treats it as such. + + Because of this blurred distinction, using the ordinary General +Public License for libraries did not effectively promote software +sharing, because most developers did not use the libraries. We +concluded that weaker conditions might promote sharing better. + + However, unrestricted linking of non-free programs would deprive the +users of those programs of all benefit from the free status of the +libraries themselves. This Library General Public License is intended to +permit developers of non-free programs to use free libraries, while +preserving your freedom as a user of such programs to change the free +libraries that are incorporated in them. (We have not seen how to achieve +this as regards changes in header files, but we have achieved it as regards +changes in the actual functions of the Library.) The hope is that this +will lead to faster development of free libraries. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, while the latter only +works together with the library. + + Note that it is possible for a library to be covered by the ordinary +General Public License rather than by this special one. + + GNU LIBRARY GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library which +contains a notice placed by the copyright holder or other authorized +party saying it may be distributed under the terms of this Library +General Public License (also called "this License"). Each licensee is +addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also compile or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + c) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + d) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the source code distributed need not include anything that is normally +distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Library General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + <one line to give the library's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Library General Public + License as published by the Free Software Foundation; either + version 2 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Library General Public License for more details. + + You should have received a copy of the GNU Library General Public + License along with this library; if not, write to the Free + Software Foundation, Inc. + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + <signature of Ty Coon>, 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! Index: src/external/gpl2/xcvs/dist/acl/INSTALL diff -u /dev/null src/external/gpl2/xcvs/dist/acl/INSTALL:1.1 --- /dev/null Thu Mar 8 15:30:39 2012 +++ src/external/gpl2/xcvs/dist/acl/INSTALL Thu Mar 8 15:30:38 2012 @@ -0,0 +1,23 @@ + +Installation + +- copy the file acl.c under src directory of CVS source distribution. + "cp acl.c /path/to/cvs-1.11.22/src/" +- copy the patch file cvsacl-patch-1.2.5 under CVS source distribution + directory. + "cp cvsacl-patch-1.2.5 /path/to/cvs-1.11.22/" +- cd to CVS source directory. + "cd /path/to/cvs-1.11.22/" +- apply the patch. + "patch -p0 < cvsacl-patch-1.2.5 +- if you are initializing the repository after applying patch, related + config files will be created with init command. + "cvs -d /path/to/repository init" +- if you already have a repository, you have to add the aclconfig file + to your $CVSROOT/CVSROOT/. aclconfig.default is the default configuration + file, you can rename it to aclconfig, and use it . +- modify aclconfig file, if you need to change some options. +- as the last step, you have to define yourself as acl administrator. + "cvs -d /path/to/repository racl yourname:p -r ALL -d ALL" + this command gives p (acl admin) rights to user (yourname), + on all repository and tags/branches. Index: src/external/gpl2/xcvs/dist/acl/README diff -u /dev/null src/external/gpl2/xcvs/dist/acl/README:1.1 --- /dev/null Thu Mar 8 15:30:39 2012 +++ src/external/gpl2/xcvs/dist/acl/README Thu Mar 8 15:30:38 2012 @@ -0,0 +1,279 @@ + +CVS Access Control List Extension Patch + +http://cvsacl.sourceforge.net/ +sba...@users.sourceforge.net + +CVSACL is a patch for CVS. It adds two new subcommands +(acl & racl) to cvs for access control list management. It +provides advanced ACL definitions per modules, directories, +and files on branch/tag for remote cvs repository connections. +Execution of all CVS subcommands can be controlled with eight +different permissions. +ACL definitions works for only remote connections, local users +can access and modify repository, if unix file system permissions +allow. If you want all users to make remote connections to +repository, and not allow local users to access repository, you +have to set CVSServerRunAsUser keyword in aclconfig file +(explained below). +Still local users can use acl and racl subcommands to set +permissions on directories or files if they have acl admin rights (p) +on related directories or files. +So, in order to control all access to repository with this ACL +extension, you should use CVSServerRunAsUser keyword and force all +users to make remote connections. CVS repository administrator or +project managers have to use acl and racl subcommands to manage +permissions. But there is no gui client supporting these subcommands, +so you have to use cvs client itself either locally or remotely. + + + + +Permission Types + +- no access + Command line character: n + If a user given n permission, it is not allowed for any action on repository. +- read + Command line character: r + r permission gives only read access on repository. + With r permission you are allowed to run cvs subcommands: annotate, + checkout, diff, export, log, rannotate, rdiff, rlog, status. +- write + Command line character: w + w permission allows only cvs commit/checkin action. + With w permission, you are not allowed to add/remove any file to/from + repository, other permissions should be defines for that. +- tag + Command line character: t + t permission allows cvs tag and rtag subcommands to run, so you may + control tagging and untagging operations. t permission includes r + permission, since without reading you can not tag/untag a file. + However t permission does not include write permission, you can not + commit a file with only t permission. +- create + Command line character: c + c permission allows cvs add and import subcommands to run. To add or + import a file/directory to repository, you have to given a c + permission. Again, c permission does not include write permission, + thus you may only add or import files, but you can not modify any + existing file. After issuing add subcommand, you have to commit the file + to complete adding. This commit subcommand is allowed because you are + adding file and not modifying existing one. +- delete + Command line character: d + d permission allows cvs remove command to run. To remove a file/directory + from repository, d permission have to set. It does not include write + permission, so you can not modify contents of an existing file on repository. +- full access except admin rights + Command line character: a + a permission gives all access (above permissions) to repository, but it + can not modify permissions. Only acl admins may modify the acl definitions. +- acl admin + Command line character: p + p permission means that user is an acl admin, so it is allowed to make anything on repository. + + +ACL Config Keywords +The administrative file aclconfig contains miscellaneous settings which +affect the behaviour of ACL extension. Currently defined keywords are: + +UseCVSACL=value +Use ACL definitions if set to yes. If you do not want to use ACLs for +some repositories in a patched CVS server, set this keyword to no. The default is no. + +UseCVSACLDefaultPermissions=value +Value can be any combination of valid permission types (w,r,t,c,d,t,a,p). +if there is no defined ACL and default permission in access file, or no +access file at all, this permissions are used. The default is p (admin rights), +if aclconfig file is created with cvs init. + +UseCVSGroups=value +CVS does not have a CVSROOT/passwd file. However it can be created manually +(format should be same as /etc/group). If value set to yes, CVS checks for +groups in file $CVSROOT/CVSROOT/group The default value is no. + +UseSystemGroups=value +Group memberships for users are checked in file /etc/group, if value is set +to yes. The default value is no. + +CVSACLFileLocation=value +Originally access file is put under CVSROOT/CVSROOT, if you want a different +location, set value to a valid path. The default value is $CVSROOT/CVSROOT/access. + +CVSGroupsFileLocation=value +IF UseCVSGroups is set to yes, CVS looks for a group file under $CVSROOT/CVSROOT. +To use a different location for group file set value to a valid path to group. +The default value is $CVSROOT/CVSROOT/group. + +UseSeparateACLFileForEachDir=value +If value is set to yes, a separate ACL file (access) is created for each +directory in repository. If you have a really big repository +(directories>10,000 and files>100,000), performance may drop due to a big +acl file, access. Setting the value to yes, may increase performance. Normally, +you will not need this. The default value is no. + +StopAtFirstPermissionDenied=value +If StopAtFirstPermissionDenied is set to yes +operation will stop at first permission denied message. +e.g. when you send commit command for a directory, if you dont +have write permission for just one file under the directory, +by default you will have a warning and commit will continue +on the other files. If you set this keyword to 'no', then +commit operation will be stopped when inaccassable file found. +Default is no. + +CVSServerRunAsUser=value +Set CVSServerRunAsUser keyword to a valid system user. +When a user make a remote connection to CVS, after successfull authentication +cvs process switch to run as that user, or defined system user in +$CVSROOT/CVSROOT/passwd. So, you also have to set unix file permissions accordingly. +A better solution: +Add a user and group such as both cvsadm. +Set CVSServerRunAsUser keyword to cvsadm. +Change unix file system permissions for your repository, +make cvsadm user and group owner, and read,write,execute permissions and setgid. +(chown cvsadm -R /path/to/your/repository) +(chgrp cvsadm -R /path/to/your/repository) +(chmod 2770 -R /path/to/your/repository) +Add yourself to cvsadm group (since you are ACL administrator). +Therefore, only users making remote connections will have access to repository +if you give rights. Local users can not access to repository via a cvs client or directly. + + +Command Line Usage Information +acl command is used on checked out files or directories. racl command is +used on repository without a working copy. Usage information can be obtained +with standard cvs --help command. +Output of cvs --help acl and cvs --help racl: + +Usage: cvs racl [user||group:permissions] [-Rl] [-r tag] + -R Process directories recursively. + -r rev Existing revision/tag. + -l List defined ACLs. + +Usage: cvs acl [user||group:permissions] [-Rl] [-r tag] + -R Process directories recursively. + -r rev Existing revision/tag. + -l List defined ACLs. + +NOTICE: there is no more -d -f options for directory and file, acl/racl +subcommands works just like other cvs subcommands. + +You may directly set permissions for a user or group or add/remove +permissions with + and - signs to/from existing permissions. +If you do not give the branch/tag information, default value of HEAD +(main branch) will be used. You have to give branch/tag name with -r option. +You may type ALL for branch/tag field. + +While checking for permissions, it goes thorough the list below. So the highest +significant permission is the first item in list. + +- permissions assigned to username for specific directory or file. +- permissions assigned to group name for specific directory or file. +- permissions as defaults for specific directory or file. +- permissions assigned to parent folders (inherits from the first parent + which permissions are assigned). +- permissions as repository defaults. +- permissions in aclconfig file. + + + + +Examples + /cvs/ + | + | + +--projectA/ + | | + | +---CVSROOT/ + | | + | +---lib/ + | | | + | | +---gnulib/ + | | | + | | +---zlib/ + | | + | +---src/ + | | | + | | +---main.c + | | | + | | +---server.c + | | | + | | +---client.c + | | + | +---gui/ + | + +--projectB/ +We have above directory structure for a cvs repository, and no defined permissions. + +Setting main default permissions: + +$ cvs -d /cvs/projectA racl cvsadmin:p -r ALL ALL +$ cvs -d /cvs/projectA racl ALL:r -r ALL ALL +User cvsadmin will be an acl admin, and all other users will have only read +rights on all branches/tags in projectA repository. This is the default acl +definition and it overwrites default permissions in $CVSROOT/CVSROOT/aclconfig file. + +$ cvs -d /cvs/projectA racl ALL:r -r ALL ALL +$ cvs -d /cvs/projectA racl ALL:n -r ALL gui +After executing these two commands, all users will have read access on all +directories and files except gui directory. Everyone will be denied to access to gui +directory becase no access, n, permissions is set. + +Setting permissions directly on a file or directory: + +$ cvs -d /cvs/projectA racl userX:wcd lib +$ cvs -d /cvs/projectA racl group1:w lib +First command will set write, create, and delete permissions for userX on directory +lib with branch HEAD (since no branch/tag information given, branch defaults to HEAD). +Second command will set only write permission for group1 on directory lib with branch HEAD. +Members of group1 will have only commit rights on lib directory, branch HEAD, they can +not add or remove any file, just modify existing files. +If userX is also a member of group1, userX will have write, create, and delete permissions +because it is specifically given these permissions. + +$ cvs -d /cvs/projectA racl userY:wcd -r develStream lib +$ cvs -d /cvs/projectA racl userY:r -r integStream lib +These commands will give wcd permissions to userY on lib directory with tag develstream, +and r permissions on lib directory with tag integStream. + +$ cvs -d /cvs/projectA racl userZ:wcd src +$ cvs -d /cvs/projectA racl userZ:r src/main.c +First command will give wcd permissions to userZ on src directory, but only read +permission on file main.c in src directory. + +Using + and - signs to set permissions on a file or directory: + +$ cvs -d /cvs/projectA racl userZ:+t src +$ cvs -d /cvs/projectA racl userZ:-cd src +$ cvs -d /cvs/projectA racl userZ:-wt src +Before the first command, userZ has wcd permissions on src directory, after issuing +command it will have wcdt permissions. Tag permission will be added. UserZ has wcdt +permissions, and we execute the second command to remove create and delete permissions. +So userZ has wt permissions. In the last command we also remove wt permissions, finally +userZ has no defined permissions left, and it will use the default permissions if set. + +Listing permissions on a file or directory: + +$ cvs -d /cvs/projectA racl -l src +$ cvs -d /cvs/projectA racl -l src +$ cvs -d /cvs/projectA racl -l src/main.c + +First command will list the permissions for src directory. +Example output: +d src HEAD | userX:wcd group1:r | defaults:r +userX and group1 has assigned permissions, all other users will have default +permissions, which is only read. + +Second command will list the permissions for files in src directory. +Example output: +f src/main.c HEAD | userX:wcd group1:r | defaults:r +f src/server.c HEAD | userX:wcd group1:r | defaults:r +f src/client.c HEAD | userX:wcd group1:r | defaults:r + +Third command will list the permissions for main.c file in src directory. +Example output: +f src/main.c HEAD | userX:wcd group1:r | defaults:r + + Index: src/external/gpl2/xcvs/dist/acl/aclconfig.default diff -u /dev/null src/external/gpl2/xcvs/dist/acl/aclconfig.default:1.1 --- /dev/null Thu Mar 8 15:30:39 2012 +++ src/external/gpl2/xcvs/dist/acl/aclconfig.default Thu Mar 8 15:30:38 2012 @@ -0,0 +1,33 @@ +# Set `UseCVSACL' to yes to use CVS ACL feature. +UseCVSACL=yes + +# Default CVS ACL Permission are to use. +#CVSACLDefaultPermissions=a + +# Default file location for CVS ACL file (access) is CVSROOT/access. +# If you want to use a different location, define it below. +#CVSACLFileLocation=/path/to/cvs/access + +# Set `UseSystemGroups' to yes to use system group definitions (/etc/group). +UseSystemGroups=yes + +# Set `UseCVSGroups' to yes to use another group file. +#UseCVSGroups=yes + +# Default file location for CVS groups file is CVSROOT/group. +# If you want to use a different location, define it below. +#CVSGroupsFileLocation=/path/to/cvs/group + +# Set UseSeparateACLFileForEachDir to yes in order to use a +# separate 'access' file for each directory. +# This increased the performance if you have really big repository. +#UseSeparateACLFileForEachDir=no + +# If StopAtFirstPermissionDenied is set to yes +# operation will stop at first permission denied message. +# Default is no. +#StopAtFirstPermissionDenied=no + +# Set CVSServerRunAsUser to a system user, in order CVS server +# to run as. +#CVSServerRunAsUser=runascvsuser