Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Matti Eiden <snaipperi@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Running sup on Ruby 1.9.2 (Arch Linux)
Date: Fri, 24 Dec 2010 23:44:08 +0200	[thread overview]
Message-ID: <AANLkTik9gqBwR29aUO0KMR5wvqOJ2OB18yZKoG72jrAb@mail.gmail.com> (raw)

Hey folks,

I somehow broke my Ruby 1.8 installation a few days ago and ended up
trying to run sup with Ruby 1.9.2. I grabbed it from git, however the
rake would fail for not finding "sup-files" and "sup-version". I
changed these two lines in the Rakefile

from

require 'sup-files'
require 'sup-version'

to

require './sup-files.rb'
require './sup-version.rb'

and a nice gem came out. Does anyone know what caused this? Has Ruby
syntax for requiring local files changed or is my system just being
weird?

Also, after installing the gem it failed to run because rubygems was
nagging I didn't have two other gems: ncurses and xapian-full.
(xapian-full is provided in arch linux by xapian-ruby-bindings).
Ncurses for 1.9.2.. I don't know if that even exists. And ncursesw
works just fine. I guess there's a method to compile the gem to ignore
dependencies? Anyway I just removed those dependencies to get it to
work. I cloned earlier my own repository of sup where I made these
changes if anybody wants to look (or get sup run on arch+ruby 1.9.2).
It's available here: http://gitorious.org/sup/ruby192-arch

Other than that, sup seems to work very well under 1.9.2! Nice job!
Matti Eiden
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


                 reply	other threads:[~2010-12-24 21:47 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=AANLkTik9gqBwR29aUO0KMR5wvqOJ2OB18yZKoG72jrAb@mail.gmail.com \
    --to=snaipperi@gmail.com \
    --cc=sup-talk@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