oats 0.0.1

data/.gitignore

@@ -0,0 +1,6 @@
+*.gem
+.bundle
+Gemfile.lock
+pkg/*
+/nbproject/private/
+.DS_Store

data/Gemfile

@@ -0,0 +1,15 @@
+source 'http://rubygems.org'
+
+unless defined?(OATS_GEM_IS_ALREADY_INCLUDED)
+  OATS_GEM_IS_ALREADY_INCLUDED = true
+
+  gemspec
+  # Include Gemfile from dir_tests
+  unless ENV['OATS_TESTS']
+    ENV['OATS_TESTS'] =  File.expand_path('oats_tests', File.dirname(__FILE__) )
+    puts "Undefined OATS_TESTS Environment variable, assuming: " + ENV['OATS_TESTS']
+  end
+  test_gemfile = $oats_execution['options'][ "_:gemfile"] if $oats_execution and $oats_execution['options']
+  test_gemfile ||= ENV['OATS_TESTS'] + '/Gemfile'
+  eval(IO.read(test_gemfile), binding) if File.exist?(test_gemfile)
+end

data/README.txt

@@ -0,0 +1,165 @@
+== Welcome to OATS
+
+The goal of the Automated Testing Project is to implement the tools,
+environment, and processes that will enable a QA team to create system
+integration regression test cases which can be executed by QA, Development
+teams, or build scripts in a simple or automated fashion.
+
+
+== License
+
+OATS is copyright 2012 Levent Atasoy and contributors. It is licensed under the
+Ruby license and the GPL. See the included LICENSE file in doc folder for
+details.
+
+
+== OATS Installation
+
+  - Install
+    - Ruby Ruby
+    - Ruby Bundler
+    - gem install oats
+
+  - On Windows_NT, some operations need handle.exe and psexec.exe to be in the
+    PATH.  These are found in PsTools Suite from
+    http://technet.microsoft.com/en-us/sysinternals
+
+  - Recommended to also install Netbeans (or another IDE of your choice)
+
+
+== Configuring OATS
+
+   OATS_HOME below refers to the oats gem installation folder
+  - Set the HOME variable C:\myDirectory
+  - Set USER PATH for ..\ruby\bin; C:\myDirectory\oats\bin
+    At this point you should be able to type 'oats' in commandline and see the
+    execution of a sample test.
+  - See OATS_HOME/doc/oats_ini.yml for customizable properties.
+  - Copy sample OATS_HOME/oats_tests folder to <yourTestFolder> and start adding your
+    own tests.
+  - Copy sample OATS_HOME/doc/oats-user.yml to HOME, and set 'dir_tests' to
+    your <yourTestFolder>
+
+
+== Using OATS with NetBeans
+
+  - Download NetBeans from http://netbeans.org/downloads
+  * NetBeans 7.1.2 or higher is not recommended, as the Ruby debugger seems
+    to have issues on it as of 05/04/2012
+  * If you install NetBeans 7/0-7.1.1, you'll need to install Ruby Plug-ins manually
+    For using only Ruby with these versions download smallest footprint of
+    NetBeans, e.g. NetBeans C/C++).
+    To install NBMs:
+      1. Download
+      http://jruby.org.s3.amazonaws.com/downloads/community-ruby/community-ruby_7_1_preview1.zip
+      2. Select Tools->Plugins from menu
+      3. Select Downloaded tab
+      4. Press Add Plugins...
+      5. Navigate to where you unzipped the nbms files
+      6. Select all files which end in .nbms (you can do this all in one selection
+         but if you include any non-nbms file it greys out the open button)
+      7. Accept and install
+
+  - Create a new Ruby project in NetBeans for OATS Framework
+  * Select "Ruby Application with Existing Sources"
+  * Use project name 'oats'.
+  * Add Folder 'lib' under the cloned 'oats' folder into 'Existing Sources'
+  * Add Folder 'oats_tests' under the cloned 'oats' folder into 'Test Folders'
+  * Add Folder <yourTestFolder> into 'Test Folders'.
+  * Select oats Project Properties -> Run
+    - Ensure your Ruby Platform is shown on the drop down list.
+    - For Main Script, select 'oats_main.rb'
+
+
+== Additional Ruby Installation Guidance For Windows
+
+  http://rubyinstaller.org/downloads/
+  https://github.com/oneclick/rubyinstaller/wiki/development-kit
+  1. Install ruby 1.8.7
+    - 1.9.x doesn't build ruby-debug-ide19
+    - gem install --pre ruby-debug-base19x for base only
+  2. Unzip the rubydev kit and copy all bin files into ..\ruby\bin
+  3. copy the devkit directory into ...\ruby
+  4. Left double-click the self-extracting executable (SFX) downloaded and
+     choose a directory to install the DevKit artifacts into.
+     For example, C:\DevKit
+  5. cd <DEVKIT_INSTALL_DIR>
+     example: cd Devkit
+  6. ruby dk.rb init to generate the config.yml
+  7. check the config file for correct version of ruby.
+  8. finally, ruby dk.rb install to DevKit enhance your installed Rubies.
+
+
+==  LibCurl Installation (Needed only if your tests would use LibCurl)
+
+ - Darwin (Mac)
+   - Install Xcode to get the headers
+
+ - Windows
+
+  http://beginrescue.blogspot.com/2010/07/installing-curb-with-ruby-191-in.html
+  http://www.gknw.de/mirror/curl/win32/old_releases/
+
+  1. gem install oauth (from command line)
+  2. download libcurl  make sure to get the one for mingw32 and that you
+     get libcurl and not plain-old curl.
+     or  get libcurl from \\opfiler\qa\oatsSetup (curl-7.21.1-devel-mingw32)
+  3. copy or extract files in C drive
+  4. copy bin files to ..\ruby\bin
+  5. gem install curb -- --with-curl-lib=C:\curl-7.21.1-devel-mingw32\bin \
+     	 --with-curl-include=C:\curl-7.21.1-devel-mingw32\include
+  6. Add  '...\curl-7.21.1-devel-mingw32\bin' to USER PATH
+
+
+
+== Ruby 1.9.X IDE Debug setup
+To use IDE debugger with 1.9.X, you will need to install 'ruby-debug19' instead
+of 'ruby-debug' gem and follow the instructions found in:
+  http://noteslog.com/post/netbeans-6-9-1-ruby-1-9-2-rails-3-0-0-debugging
+It instructs you to apply the following patch to:
+(Ruby folder)/lib/ruby/gems/1.9.1/gems/ruby-debug-ide19-0.4.12/bin/rdebug-ide.rb
+ #  noteslog.com, 2010-09-17 -> !!!
+ # 78 Debugger::PROG_SCRIPT = ARGV.shift
+ script = ARGV.shift
+ Debugger::PROG_SCRIPT = (script =~ /script([\\\/])rails/ ? Dir.pwd + $1 : '') + script
+
+
+== Selenium IDE
+
+Though not required for OATS execution you need to download and install the
+latest Selenium IDE plug- in from http://seleniumhq.org/download/, or from the
+list of Firefox plugins in order to create and run tests via the Selenium IDE on
+Firefox.  Read the IDE documentation at http://seleniumhq.org to learn about IDE
+usage.
+To use Chrome with Webdriver, download and put the chromedriver applicable to
+your machine in the PATH for OATS.
+
+
+== MySQL Client
+
+If your tests interact with MySQL, then you need to install a MySQL client which
+is the default DB interface provided by OATS. Many of the OATS tests require
+interaction with the various RL applicaton MySQL databases.  In order to
+interact with the MySQL databases on various environments, OATS expects to find
+the MySQL client in the PATH. To verify this, open a Windows CMD window and type
+'mysql \--help'. If you see an error message instead of MySQL help, make sure
+MySQL is installed on your system and that the bin directory of MySQL is
+included in the PATH.
+
+
+== Putty and Pageant (For Windows-OCC and Windows-Agent Installations)
+
+Installation of PuTTY, Pageant, Puttygen, and Plink are necessary if your tests
+require access to systems via ssh. For Linux systems the default methods used by
+OATS to interrogate logs or execute scripts on remote is via Plink, using ssh.
+Pageant is also useful to install if you are using tortoise to access SVN setup
+with SSH.
+
+  1. Download and install PuTTY, Pageant, Puttygen, and Plink from
+     http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. These are
+     standalone executables, so you can install them wherever you'd like.
+  2. Once the PUTTY is installed, append <putty-installation-dir>/PuTTY to
+     the user environment variable PATH (create it if it does not exist.)
+  3. Use PuTTYgen to Generate Public and Private Keys, and incorporate them
+     in your appropriate authorized_keys files and .ssh folders
+

data/Rakefile

@@ -0,0 +1,2 @@
+require 'rubygems'
+require "bundler/gem_tasks"

data/bin/agent

@@ -0,0 +1,204 @@
+#!/bin/bash
+# This script is used to start OATS in agent mode and communicate with OCC.
+
+[ "$OS" ] || export OS=$(uname)
+if [ "$OS" == "Windows_NT" ]; then
+    export PATH="$PATH:/cygdrive/c/apps/cygwin/bin"
+    [ "$HOSTNAME" ] || HOSTNAME="$COMPUTERNAME"
+else
+    [ "$HOSTNAME" ] || HOSTNAME=`hostname`
+fi
+export HOSTNAME
+[ "$OATS_AGENT_NICKNAME" ] || OATS_AGENT_NICKNAME=${HOSTNAME/.*}
+doc="
+Starts OATS agent to be used with OCC
+
+USAGE: agent [-k[ill]] [-n[ickname] OATS_AGENT_NICKNAME] [ -p[ort]  OATS_AGENT_PORT ]
+             [ -r[epo] OATS_REPOSITORY_VERSION ] [ -u OATS_USER]
+
+Parameters: (also can be passed in via environment variables
+ -n OATS_AGENT_NICKNAME OCC ID of the agent.
+ -p OATS_AGENT_PORT Agent port to communicate with OCC. Default is port previously
+    used for OATS_AGENT_NICKNAME.
+ -u OATS_USER who started the agent. Used for logging purposes only.
+ -r OATS_REPOSITORY_VERSION Required to update the agent.
+ -k kill the agent, or set OATS_KILL_AGENT
+ -d DISPLAY_NUM Number of the VNC Display, for Linux only
+
+Example:
+/home/occadmin/oats/bin/agent -p 3011 -n occ_1 -r 403cc620c265db84dbd3fb7d7cce4d57416bff09
+
+The agent script should be in the path so that ssh from occ can pick it up.
+Git requires definition of OATS_GIT_REPOSITORY environment variable.
+ "
+input_pars="$@"
+while [ "$1" ]; do
+    case $1 in
+	-p*) shift; OATS_AGENT_PORT="$1" ;;
+	-n*) shift; OATS_AGENT_NICKNAME="$1" ;;
+	-u*) shift; OATS_USER="$1" ;;
+	-k*) OATS_KILL_AGENT='OATS_KILL_AGENT' ;;
+	-r*) shift; OATS_REPOSITORY_VERSION="$1" ;;
+	-d*) shift; DISPLAY_NUM="$1" ;;
+	*) echo "Unrecognized parameter: $1" ;
+	    echo "$doc"
+	    exit ;;
+    esac
+    shift
+done
+
+function agent_echo {
+    echo "$(date +'%m/%d/%H:%M:%S') $*"
+}
+function fkill {
+    agent_echo "Killing PID: $each_pid"
+    if [ "$OS" == "Windows_NT" ]; then
+	pskill $1
+    else
+	kill -9 $1
+    fi
+}
+
+{
+    agent_echo  "$0 $input_pars"
+
+    if [ -n "$(echo "$GEM_HOME" | grep ruby-1.9.2)" ]; then
+    # If spawned from OCC, running 1.9.2, we need to switch to 1.8 since
+    # can't run oauth in 1.9.2. Assume RVM is installed and the system ruby is 1.8.X
+	if [ -n "$(echo "$rvm_ruby_global_gems_path" | grep ruby-1.9.2)" ] && [[ -s "$HOME/.rvm/scripts/rvm" ]]; then
+	    source "$HOME/.rvm/scripts/rvm" # Load RVM function
+	    rvm system
+	fi
+    fi
+    # Need these off when called by OCC
+    unset BUNDLE_BIN_PATH BUNDLE_GEMFILE GEM_HOME GEM_PATH MY_RUBY_HOME # RAILS_ENV
+    unset RUBYOPT
+    if [ -z "$OATS_HOME" ]; then
+	cd $(dirname $(type -p $0))/..
+	OATS_HOME=$PWD
+    fi
+    [ "$OATS_GIT_REPOSITORY" ] && OATS_HOME="$HOME/results_archive/$OATS_AGENT_NICKNAME"/oats
+    export OATS_HOME
+    export OATS_AGENT_LOGFILE="$logFile"
+    oats_bin="$OATS_HOME/bin"
+#    [ "$OS" == "Windows_NT" ] && oats_bin=$(cygpath -w $oats_bin)
+#    ruby_com="$oats_bin/oats -n $OATS_AGENT_NICKNAME -p $OATS_AGENT_PORT"
+    ruby_com="oats -n $OATS_AGENT_NICKNAME -p $OATS_AGENT_PORT"
+    export PATH="$PATH:$OATS_HOME/bin:$OATS_HOME/bin/$OS"
+    if [ -e "$config_agent_file" ]; then
+	line=$(grep "^$OATS_AGENT_NICKNAME" "$config_agent_file")
+	read nickname PREV_OATS_AGENT_PORT pid display<<< $line
+	[ "$OATS_AGENT_PORT" ] || OATS_AGENT_PORT=$PREV_OATS_AGENT_PORT
+	[ "$PID" ] || PID=$pid
+	if [ -z "$DISPLAY_NUM" ]; then
+	    if [ "$display" ]; then
+		DISPLAY_NUM=$(echo "$display" | sed -e 's/.*:\(.\).*/\1/')
+		[ "$DISPLAY_NUM" ] || DISPLAY_NUM="$display"
+	    else
+		DISPLAY_NUM='0'
+	    fi
+	fi
+    fi
+    if [ -z "$OATS_AGENT_PORT" ]; then
+	agent_echo "$0: Must specify a port, exiting..." >&2
+    exit 1
+    fi
+
+    [ "$OATS_AGENT_PORT" == "$PREV_OATS_AGENT_PORT" ] && PREV_OATS_AGENT_PORT=''
+    for OATS_AGENT_PORT_VAR in $PREV_OATS_AGENT_PORT $OATS_AGENT_PORT; do
+	skip_port=''
+	if [ "$PID" -a "$OATS_AGENT_PORT_VAR" == "$PREV_OATS_AGENT_PORT" ]; then
+            agent_echo "Attempting to kill agent $OATS_AGENT_NICKNAME with PID: $PID"
+	    fkill $PID
+	    [ $? == 0 ] && skip_port=skip_port
+	fi
+	if [ -z "$skip_port" ]; then
+	    # agent_echo "Attempting to kill process holding on to port $OATS_AGENT_PORT_VAR"
+	    if [ "$OS" == Darwin ]; then
+		lines=$(ps -ef|grep "$ruby_com"|grep -v grep)
+		PID=$(echo $(cut -c 6-11 <<< "$lines"))
+	    else
+		if [ "$OS" == Windows_NT ]; then # Killing the top level bash process doesn't cut it
+		    lines=$(netstat -a -o 2>/dev/null| grep "$OATS_AGENT_PORT_VAR .* LISTEN" )
+		else
+		    lines=$(netstat -n -p -l 2>/dev/null| grep "$OATS_AGENT_PORT_VAR .* LISTEN" )
+		fi
+		PID=$(echo "$line" | sed 's/.* LISTEN[^ ]* *//;s/.ruby .*//')
+		[ "$PID" -a "$PID" != "$line" ] || PID=''
+	    fi
+	    if [ "$PID" ]; then
+		agent_echo "PS line(s): $lines"
+		for each_pid in $PID; do
+		    fkill $each_pid
+		done
+	    # else
+	    # 	agent_echo "No agent is found on port $OATS_AGENT_PORT_VAR"
+	    fi
+	fi
+    done
+    [ "$OATS_KILL_AGENT" ] && return
+
+    if [ "$OATS_GIT_REPOSITORY" ]; then
+	[ -d $OATS_HOME ] || git clone $OATS_GIT_REPOSITORY $OATS_HOME
+	cd $OATS_HOME
+        origin="$OATS_GIT_REPOSITORY"
+        [ "$origin" ] || origin=origin
+	if [ "$OATS_REPOSITORY_VERSION" ]; then
+	    for i in 1 2; do
+		out=$(git checkout $OATS_REPOSITORY_VERSION 2>&1) && break # may detach HEAD, but it is OK
+		if [ "$out" == "fatal: reference is not a tree: $OATS_REPOSITORY_VERSION" ]; then
+		    echo -n "Need to pull requested version: $OATS_REPOSITORY_VERSION "
+		else
+		    echo "$out"
+		fi
+		git pull $origin master # fast-forward master from origin
+	    done
+        else
+            git pull $origin master # fast-forward master from origin
+	fi
+	OATS_CODE_VERSION=$(git rev-list HEAD -1) # last commit in checked out version
+	if [ "${OATS_CODE_VERSION##$OATS_REPOSITORY_VERSION*}" ]; then
+	    agent_echo "Could not update the code version $OATS_CODE_VERSION to $OATS_REPOSITORY_VERSION" >&2
+	    return 2
+	fi
+	[ "$OATS_REPOSITORY_VERSION" ] || agent_echo "Using OATS code version: $OATS_CODE_VERSION"
+    elif [ -d .svn ]; then
+	COUNTER=0
+	[ "$OATS_REPOSITORY_VERSION" ] && agent_echo "Requested OATS Version: $OATS_REPOSITORY_VERSION"
+	while [ $COUNTER -lt 5 ]; do
+            let COUNTER=COUNTER+1
+	    OATS_CODE_VERSION=$(svn info $OATS_HOME | sed -n 's/Last Changed Rev: *//p')
+	    [ "$OATS_REPOSITORY_VERSION" ] || break
+	    [ "$OATS_CODE_VERSION" -ge "$OATS_REPOSITORY_VERSION" ] && break
+	    [ $COUNTER -eq 1 ] || sleep 3
+	    svn update $OATS_HOME 2>&1
+	done
+	if [ $COUNTER -eq 5 ]; then
+	    agent_echo "Could not update the code version $OATS_CODE_VERSION to $OATS_REPOSITORY_VERSION" >&2
+	    return 2
+	fi
+	agent_echo "Current OATS code version: $OATS_CODE_VERSION"
+    else
+	OATS_CODE_VERSION=$OATS_REPOSITORY_VERSION
+	[ "$OATS_CODE_VERSION" ] && agent_echo "Setting OATS code version to the requested version: $OATS_CODE_VERSION]" # This is not set for development/debug
+    fi
+    export OATS_CODE_VERSION
+#    echo "$OATS_AGENT_NICKNAME $OATS_AGENT_PORT" >| $config_agent_file
+    if [ "$OS" == "Linux" ]; then # Do this with VNC displays
+	# Allocate 2x as display. VNC takes 592x, vino takes next available from 59++
+#	vnc_num="2$(echo $OATS_AGENT_PORT | cut -c 4)"
+	vnc_num="$DISPLAY_NUM"
+	[ "$vnc_num" ] || vnc_num="1"
+	pgrep -fl "Xvnc4 :$vnc_num" >/dev/null || vncserver :$vnc_num -SecurityTypes=None -geometry 1900x1060
+	export DISPLAY=":$vnc_num.0"
+	agent_echo "Setting DISPLAY to $DISPLAY"
+    fi
+    cd $OATS_HOME  # Needed for bundler
+    agent_echo "Starting agent $OATS_AGENT_NICKNAME on port $OATS_AGENT_PORT"
+    $ruby_com
+} >> $LOGFILE 2>&1 &
+
+PID=$(jobs -p)
+echo "Initiated PID: $PID"  >> $LOGFILE
+echo "$PID"
+echo "$OATS_AGENT_NICKNAME $OATS_AGENT_PORT $PID $DISPLAY_NUM"  >| $CONFIG_FILE

data/bin/oats

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+dir = File.dirname(__FILE__)
+$:.push File.expand_path('../lib', dir )
+require 'oats'
+if $oats_execution['options']["_:agent"]
+  Oats::Driver.agent
+else
+  Oats.run
+end

data/bin/occ

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+#
+# This script is used to start OCC
+
+#[ "$RAILS_ENV"  ] || export RAILS_ENV="production"
+occ_home = ENV['OATS_OCC_HOME']
+unless occ_home
+  pwd = Dir.pwd
+  occ_home = pwd if File.basename(pwd) == 'occ'
+end
+occ_home = ENV['HOME'] + '/occ' unless occ_home
+occ_home = ENV['HOME'] + '/NetBeansProjects/occ' unless File.directory?(occ_home)
+
+raise "Must define OCC_HOME or be in occ directory to run this command." unless occ_home
+
+Dir.chdir(occ_home)
+exec 'ruby script/rails server mongrel' # -p 4000
+
+# By pass the following unless using distributed agents
+#  if [ "$OS" != "Windows_NT" ]; then
+#    if  [ -z "$SSH_AGENT_PID" ] || ! ps -ef | grep ${SSH_AGENT_PID} | grep ssh-agent$ > /dev/null ; then
+#      echo "Should start_agent for SSH first"
+#      # exit 1
+#      fi
+#      ssh-add -l ||  echo "*** WARNING *** Please add your ssh keys ssh-add"
+#      fi
+
+
+#mongrel_rails start -e production -p 3000 --log log\production.log

data/bin/results_cleanup

@@ -0,0 +1,6 @@
+#!/bin/bash
+rm -fr  ~/results
+cd ~/results_archive
+rm -fr */8*  # Cleanup older dated results 
+rm -f */agent_logs/ag*_*.log  # cleanup old agent logs 
+rm -fr incomplete

data/doc/COPYING

@@ -0,0 +1,55 @@
+Open Automated Testing System (OATS) is copyrighted free software by Levent Atasoy
+<Levent.Atasoy at gmail dot com> and contributors. 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).  But some files in the distribution
+   are not written by the author, so that they are not under this terms.
+
+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.
+
+

data/doc/LICENSE

@@ -0,0 +1,55 @@
+Open Automated Testing System (OATS) is copyrighted free software by Levent Atasoy
+<Levent.Atasoy at gmail dot com> and contributors. 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).  But some files in the distribution
+   are not written by the author, so that they are not under this terms.
+
+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.
+
+