From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] ncursesw encoding
Date: Thu, 25 Nov 2010 15:50:21 +0200 [thread overview]
Message-ID: <1290692520-sup-6531@tilus.net> (raw)
In-Reply-To: <4CEE4DBF.7030600@kpvn.de>
Moritz Neeb, 2010-11-25 13:51:
> I installed sup as a debian package, not as gem. Could this be a
> problem?
I don't know. Though I wouldn't be surprised if it turns out to be.
Rubygems and Dpkg provide essentially the same service (package and
dependency management) and are (afaik) not aware of each other. As a
result they do not play together at all. Usually there are no
collisions but ymmv.
On Debian derivatives my route of least gray hair has been to install
Rubygems from sources using defaults and as much of the Ruby stuff
from gems as possible.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-11-25 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 17:54 Moritz Neeb
2010-11-24 19:09 ` Tero Tilus
2010-11-25 11:51 ` Moritz Neeb
2010-11-25 13:50 ` Tero Tilus [this message]
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=1290692520-sup-6531@tilus.net \
--to=tero@tilus.net \
--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