depengine 0.0.1

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/LICENSE.LGPLv3

@@ -0,0 +1,165 @@
+		   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions. 
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version. 
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  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 that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser 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 as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/README

@@ -0,0 +1,94 @@
+Log4r - A flexible logging library for Ruby
+
+
+This release:      1.1.8 - ALPHA
+Release date:      XX/Jun/2010
+License:           LGPLv3
+Maintainer:        Colby Gutierrez-Kraybill
+Contributors:      Leon Torres               Original Maintainer
+                   Martain Stannard          RollingFileOutputter
+                   Steve Lumos               SyslogOutputter
+                   Andreas Hund              YamlConfigurator
+                   Jamis Buck                log4r.gemspec
+                   Charles Strahan           log4jxml/chainsaw integration
+                   Nitay Joffe               STARTTLS
+                   David Siegal              Smart updates to RollingFileOutputter
+Homepage:          http://log4r.rubyforge.org/
+Download:          http://rubyforge.org/frs/?group_id=203
+
+Summary
+-------
+
+Log4r is a comprehensive and flexible logging library written in Ruby for use 
+in Ruby programs. It features a hierarchical logging system of any number of 
+levels, custom level names, logger inheritance, multiple output destinations 
+per log event, execution tracing, custom formatting, thread safteyness, XML 
+and YAML configuration, and more.
+
+
+Requirements
+------------
+
+* (required) Ruby >= 1.7.0 (use log4r 1.0.2 for Ruby 1.6)
+* (optional) RubyGems for installing Log4r as a gem
+* (optional) Ruby syslog library for SyslogOutputter
+* (optional) XML configuration requires REXML
+* (optional) log4j chainsaw integration requires 'builder' >= 2.0
+* (optional) STARTTLS email login, requires 'smtp_tls" if Ruby <= 1.8.6
+
+
+More Info
+---------
+
+* Installation instructions are in the file INSTALL
+
+* Comprehensive examples are provided in examples/ and can be run right away
+
+* Log4r homepage: doc/index.html
+  Online: http://log4r.rubyforge.org/
+
+* Manual: doc/manual.html
+  Online: http://log4r.rubyforge.org/manual.html
+  
+* RDoc API reference: doc/rdoc/index.html 
+  Online: http://log4r.rubyforge.org/rdoc/index.html
+  
+* The changelog
+
+* Log4r is hosted by RubyForge, which provides news, bug tracking and a forum
+
+* Feel free to bug the maintainer with any questions (listed at top of file)
+
+
+Usability
+---------
+
+Log4r works really well, so please take advantage of it right away! :)
+All versions since 0.9.2 have been stable and backward-compatible. The
+code is stable enough that updates are infrequent and usually only for
+adding features or keeping the code up to date with Ruby.
+
+
+Platform Issues
+---------------
+
+Log4r is known to work on Linux and WindowsXP. It's safe to assume that Log4r 
+will work on any Ruby-supported platform.
+
+
+When Trouble Strikes
+--------------------
+
+Log4r comes with an internal logger. To see its output, create a logger
+named 'log4r' before any others and give it a suitable outputter,
+
+  trouble = Logger.new['log4r']
+  trouble.add Outputter.stdout
+
+Try running the unit tests provided (run the file tests/runtest.rb). Let
+the maintainer know what's up and feel free to explore and fix the 
+code yourself. It's well documented and written in Ruby. :)
+
+Also, try out the bug/request tracking system at 
+http://rubyforge.org/tracker/?group_id=203
+

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/Rakefile

@@ -0,0 +1,74 @@
+
+# $Id$
+
+# incorporated from Revolution Health version of log4r
+
+require 'rubygems'
+require 'rake/gempackagetask'
+require 'rubygems/specification'
+require 'date'
+require 'fileutils'
+
+GEM = "log4r"
+GEM_VERSION = "1.1.8"
+AUTHOR = "Colby Gutierrez-Kraybill"
+EMAIL = "colby@astro.berkeley.edu"
+HOMEPAGE = %q{http://log4r.rubyforge.org}
+SUMMARY = "Log4r, logging framework for ruby"
+DESCRIPTION = "See also: http://logging.apache.org/log4j"
+DIRS = [ "doc/**/*", "examples/**/*", "lib/**/*", "tests/**/*" ]
+
+spec = spec = Gem::Specification.new do |s|
+  s.name = GEM
+  s.rubyforge_project = s.name
+  s.version = GEM_VERSION
+  s.platform = Gem::Platform::RUBY
+  s.has_rdoc = true
+  s.extra_rdoc_files = ["README", "LICENSE", 'TODO']
+  s.summary = SUMMARY
+  s.description = DESCRIPTION
+  s.author = AUTHOR
+  s.email = EMAIL
+  s.homepage = HOMEPAGE
+
+  # Uncomment this to add a dependency
+  # s.add_dependency "foo"
+
+  s.require_path = 'lib'
+  s.files = %w(LICENSE LICENSE.LGPLv3 README INSTALL Rakefile TODO)
+  s.files = s.files + DIRS.collect do |dir|
+    Dir.glob( dir )
+  end.flatten.delete_if { |f| f.include?("CVS") }
+end
+
+Rake::GemPackageTask.new(spec) do |pkg|
+  pkg.gem_spec = spec
+end
+
+desc "install the gem locally"
+task :install => [:package] do
+  sh %{sudo gem install pkg/#{GEM}-#{GEM_VERSION}}
+end
+
+desc "create a gemspec file"
+task :make_spec do
+  File.open("#{GEM}.gemspec", "w") do |file|
+    file.puts spec.to_ruby
+  end
+end
+
+# require 'test/unit'
+
+# TODO: integrate unit tests
+#task :test do
+#  FileUtils.mkdir(File.join(File.dirname(__FILE__), %w[log])) if !File.exists?(File.join(File.dirname(__FILE__), %w[log]))
+#  FileUtils.rm(Dir.glob(File.join(File.dirname(__FILE__), %w[log *])))
+#  runner = Test::Unit::AutoRunner.new(true)
+#  runner.to_run << 'test'
+#  runner.pattern = [/_test.rb$/]
+#  exit if !runner.run
+#end
+
+task :default => [:package] do
+end
+

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/TODO

@@ -0,0 +1,2 @@
+
+

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/doc/content/contact.html

@@ -0,0 +1,22 @@
+Title: Log4r - Contact
+Template: main.html
+Id: $Id$
+
+<tr><td width="100%" class="contenttitle">Contact the Developers</td></tr>
+<tr><td width="100%" class="contentbuff">&nbsp;</td></tr>
+<tr><td width="100%" class="content">
+Lead developer:
+<p>
+Leon Torres 
+&lt;leon(at)ugcs dot caltech dot edu</a>&gt;
+<br/>
+Pasadena, CA, USA (UTC-8)
+<p/>
+Contributors:
+<ul>
+  <li>Martain Stannard - for RollingFileOutputter and for caring about maintenance
+  <li>Steve Lumos - for SyslogOutputter
+  <li>Jamis Buck - for making Log4r available as a RubyGems gem
+  <li>Andreas Hund - for YAML configuration with YamlConfigurator
+</ul>
+</td></tr>

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/doc/content/contribute.html

@@ -0,0 +1,21 @@
+Title: Log4r - Contribute
+Template: main.html
+Id: $Id$
+
+<tr><td width="100%" class="contenttitle">Contributing to Log4r</td></tr>
+<tr><td width="100%" class="contentbuff">&nbsp;</td></tr>
+<tr><td width="100%" class="content">
+If you wish to contribute something to Log4r or assist in development,
+please drop an email to Leon: leon(at)ugcs dot caltech dot edu</a>. There
+will always be work to do. Some things that come to mind are:
+<p/>
+
+<font size="-1">
+<ul>
+<li> Find bugs and flaws, or areas to improve
+<li> More Outputters that do various nifty things
+<li> More and better documentation
+<li> And, of course, spreading the good word <code>;-)</code>
+</ul>
+</font>
+</td></tr>

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/doc/content/index.html

@@ -0,0 +1,90 @@
+Title: Log4r - Manual
+Template: main.html
+Id: $Id$
+
+<tr><td width="100%" class="contenttitle">A Powerful Logging Library for Ruby
+</td></tr>
+<tr><td width="100%" class="contentbuff">&nbsp;</td></tr>
+<tr><td width="100%" class="content">
+
+<h4 class="header">What Log4r Is</h4>
+Log4r is a comprehensive and flexible logging library written in Ruby
+for use in Ruby programs. It features a hierarchical logging system
+of any number of levels, custom level names, logger inheritance,
+multiple output destinations, execution tracing, custom formatting, thread
+safteyness, XML and YAML configuration, and more.
+<p/>
+Log4r is an adherent to the philosophy of logging using simple print 
+statements. What Log4r adds to this philosophy is a flexible way of 
+controling the information being logged. Log information can be sent to
+any kind of destination and with varying degrees of importance. Log4r is 
+designed so that logging statements can remain in production code with
+almost no extra computational cost.
+<p/>
+Log4r intends to be easy to use and configure, no matter the complexity.
+Casual scripts can use Log4r right away with minimal configuration, while
+more sophisticated applications can set up a structured configuration file 
+in XML or YAML. Comprehensive documentation is provided, with a user's manual,
+a reference API, and over a dozen examples. Log4r attempts to abide by the 
+Principle of Least Surprise, which means that it works as intended at all 
+points.
+<p/>
+Log4r was inspired by and provides much of the features of the
+<a href="http://jakarta.apache.org/log4j/docs/index.html">Apache Log4j</a> 
+project, but is not a direct implementation or clone. Aside from superficial
+similarities, the projects are not related in any way and the code base is 
+completely distinct. Log4r was developed without even looking at the 
+Apache Log4j code.
+<p/>
+Log4r is an Open Source project and intends to remain that way. The Log4r
+license is similar to the Ruby Language license. It resides on
+<a href="license.html">this page</a> and in the distribution in a file
+named LICENSE.
+
+<!--
+<p><hr noshade color="#AA0000">
+<h4 class="header">But Why?</h4>
+
+Why a logging system like Log4r? 
+<p/>
+
+There are many non-obvious reasons. First,
+logging should not be confused with Unit testing. Unit testing and logging are
+complementary rather than exclusive. Second, logging provides a handy way
+for a program to provide useful information about itself to different 
+audiences. With logging, your application's state can be tracked over time and
+not be a complete mystery. With Log4r, you can control the amount and type of
+information that show up without having to comment out the logging statements 
+in your code. This helps reduce noise and maximize the usefulness of log files.
+Finally, logging is extremely useful in applications that are not all in one
+place (distributed). If you want to debug a client and server at the same time,
+a logging system like Log4r becomes critical.
+-->
+
+<p><hr noshade color="#AA0000">
+<h4 class="header">Getting Started with Log4r</h4>
+
+<ol>
+<li> Download the latest version from
+<a href="http://sourceforge.net/project/showfiles.php?group_id=43396">this page</a>
+<li> Try out the examples in the <tt>examples</tt> directory of the distribution
+<li> Install by running <tt>ruby install.rb</tt>
+<li> Read the nice <a href="manual.html">manual</a>
+<li> Use Log4r
+<li> Consult the <a href="rdoc/index.html">Log4r RDoc API</a> for reference
+<li> <a href="http://www.ruby-lang.org/en/raa-list.rhtml?name=REXML">
+Get REXML</a> to take advantage of the XML config
+<li> <a href="contribute.html">Contribute</a>!
+</ol>
+
+<h4 class="header">Install Using RubyGems</h4>
+
+<p>
+If you have <a href="http://rubygems.rubyforge.org/wiki/wiki.pl?RubyGems">RubyGems</a>, install the Log4r gem!
+
+<ul>
+  <li> gem --remote-install log4r
+</ul>
+</p>
+
+</td></tr>

data/etc/isolate/ruby-1.8/gems/log4r-1.1.8/doc/content/license.html

@@ -0,0 +1,56 @@
+Title: Log4r License
+Template: main.html
+Id: $Id$
+
+<tr><td width="100%" class="contenttitle">Log4r License</td></tr>
+<tr><td width="100%" class="contentbuff">&nbsp;</td></tr>
+<tr><td width="100%" class="content">
+<pre>
+Log4r is copyrighted free software by Leon Torres &lt;leon@ugcs.caltech.edu&gt;.
+You can redistribute it and/or modify it under either the terms of the GPL, 
+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. 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.
+</pre>
+</td></tr>