From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] Instructions for testing sup with recent ruby/gems
Date: Fri, 18 Nov 2011 21:14:27 +0000 [thread overview]
Message-ID: <1321650789-sup-7136@stapelberg.de> (raw)
Hi,
Since I just figured out how to install ruby and sup’s dependencies in a clean
environment using RVM (no big deal, but…), I thought I’d share the instructions:
bash < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer)
rvm reload
rvm install 1.9.3
rvm 1.9.3
rvm gemset create sup2011-11-18
rvm 1.9.3@sup2011-11-18
rvm 1.9.3@sup2011-11-18 do gem install ncursesw
rvm 1.9.3@sup2011-11-18 do gem install trollop
rvm 1.9.3@sup2011-11-18 do gem install gettext
rvm 1.9.3@sup2011-11-18 do gem install rmail
rvm 1.9.3@sup2011-11-18 do gem install lockfile
rvm 1.9.3@sup2011-11-18 do gem install mime-types
rvm 1.9.3@sup2011-11-18 do gem install xapian-ruby
git clone git://gitorious.org/sup/mainline
cd mainline
ruby -Ilib bin/sup
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
reply other threads:[~2011-11-18 21:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1321650789-sup-7136@stapelberg.de \
--to=michael+sup@stapelberg.de \
--cc=sup-devel@rubyforge.org \
/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