Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] Kill thread doesn't seem to work
Date: Wed, 19 Mar 2008 08:51:29 -0600	[thread overview]
Message-ID: <1205937908-sup-4264@tangerine.lanl.gov> (raw)
In-Reply-To: <1205935094-sup-6162@k-desktop.int.clarkparsia.com>

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


  reply	other threads:[~2008-03-19 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 16:50 Kendall Grant Clark
2008-03-19  2:16 ` William Morgan
2008-03-19 13:59   ` Kendall Grant Clark
2008-03-19 14:51     ` John Bent [this message]
2008-03-19 15:17       ` Kendall Grant Clark
2008-03-19 16:20     ` William Morgan
2008-03-19 16:45       ` Kendall Grant Clark
2008-03-19 15:20   ` Kendall Grant Clark
2008-03-19 15:24     ` Giorgio Lando
2008-03-19 19:23       ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1205937908-sup-4264@tangerine.lanl.gov \
    --to=johnbent@lanl.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox