From mboxrd@z Thu Jan  1 00:00:00 1970
From: johnbent@lanl.gov (John Bent)
Date: Wed, 19 Mar 2008 08:51:29 -0600
Subject: [sup-talk] Kill thread doesn't seem to work
In-Reply-To: <1205935094-sup-6162@k-desktop.int.clarkparsia.com>
References: <1205772559-sup-6593@k-desktop.int.clarkparsia.com>
	<1205892920-sup-9762@south>
	<1205935094-sup-6162@k-desktop.int.clarkparsia.com>
Message-ID: <1205937908-sup-4264@tangerine.lanl.gov>

Excerpts from Kendall Grant Clark's message of Wed Mar 19 07:59:14 -0600 2008:
> I'm a Python programmer, only marginally a Ruby src code reader... Is
> there some kind of sandbox I can use to test the git next version,
> w/out borking my existing (and working, except for this one issue) sup
> install?
> 
So this is from: http://sup.rubyforge.org/wiki/wiki.pl?Contributing
I set this up previously, so I'm not positive about the initial setup
syntax but the rest of it is definitely correct:

# initial setup
git clone git://repo.or.cz/sup.git 
git branch --track next origin/next
git checkout next

# getting current, building, running local copy
git pull
rake gem
ruby -I lib -w bin/sup

This will then use a local next version w/out affecting your existing sup
install.  If you then decide you want to fully install the next version:
sudo gem install pkg/sup-999.gem

John