From: Mark Alexander <marka@pobox.com>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup install error
Date: Wed, 03 Mar 2010 21:10:31 -0500 [thread overview]
Message-ID: <1267668438-sup-218@r50p> (raw)
In-Reply-To: <1267654880-sup-4875@zyrg.net>
Excerpts from Rich Lane's message of Wed Mar 03 17:23:06 -0500 2010:
> I'm thinking about changing the gem dependency from ncursesw back to
> plain ncurses to avoid these install failures. Anyone have thoughts on
> this?
It could be that I'm misunderstanding something, but wouldn't it
still be likely that there would be failures if the user hasn't
installed the libncurses5-dev package, or whatever it's called
on their OS?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-03-04 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 21:26 John Bent
2010-03-01 21:57 ` John Bent
2010-03-01 23:50 ` John Bent
2010-03-03 22:23 ` Rich Lane
2010-03-03 22:25 ` John Bent
2010-03-04 2:10 ` Mark Alexander [this message]
2010-03-04 11:45 ` Helge Titlestad
2010-03-04 16:59 ` Rich Lane
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=1267668438-sup-218@r50p \
--to=marka@pobox.com \
--cc=rlane@club.cc.cmu.edu \
--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