From afea6f4706e5ea681fe6a6bc347abbe698427ac1 Mon Sep 17 00:00:00 2001 From: zzak Date: Tue, 5 Feb 2013 20:52:28 +0000 Subject: * doc/rubygems/*: Removed outdated documentation files * lib/rubygems/LICENSE.txt: Include license file * lib/rubygems.rb: Move Gem module documentation so rdoc can parse it and link to LICENSE.txt * lib/rubygems/*: Hide useless documentation from Gem module rdoc git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@39079 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- lib/rubygems/LICENSE.txt | 53 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 lib/rubygems/LICENSE.txt (limited to 'lib/rubygems/LICENSE.txt') diff --git a/lib/rubygems/LICENSE.txt b/lib/rubygems/LICENSE.txt new file mode 100644 index 0000000000..db88c5e118 --- /dev/null +++ b/lib/rubygems/LICENSE.txt @@ -0,0 +1,53 @@ +RubyGems is copyrighted free software by Chad Fowler, Rich Kilmer, Jim +Weirich and others. You can redistribute it and/or modify it under +either the terms of the GPL (see the GPL.txt file), or the conditions +below: + + 1. You may make and give away verbatim copies of the source form of the + software without restriction, provided that you duplicate all of the + original copyright notices and associated disclaimers. + + 2. You may modify your copy of the software in any way, provided that + you do at least ONE of the following: + + a) place your modifications in the Public Domain or otherwise + make them Freely Available, such as by posting said + modifications to Usenet or an equivalent medium, or by allowing + the author to include your modifications in the software. + + b) use the modified software only within your corporation or + organization. + + c) rename any non-standard executables so the names do not conflict + with standard executables, which must also be provided. + + d) make other distribution arrangements with the author. + + 3. You may distribute the software in object code or executable + form, provided that you do at least ONE of the following: + + a) distribute the executables and library files of the software, + together with instructions (in the manual page or equivalent) + on where to get the original distribution. + + b) accompany the distribution with the machine-readable source of + the software. + + c) give non-standard executables non-standard names, with + instructions on where to get the original software distribution. + + d) make other distribution arrangements with the author. + + 4. You may modify and include the part of the software into any other + software (possibly commercial). + + 5. The scripts and library files supplied as input to or produced as + output from the software do not automatically fall under the + copyright of the software, but belong to whomever generated them, + and may be sold commercially, and may be aggregated with this + software. + + 6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR + IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + PURPOSE. -- cgit v1.2.3