From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs110538fga; Thu, 4 Mar 2010 08:59:53 -0800 (PST) Received: by 10.224.43.151 with SMTP id w23mr1268449qae.235.1267721989107; Thu, 04 Mar 2010 08:59:49 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si1071237qwb.10.2010.03.04.08.59.48; Thu, 04 Mar 2010 08:59:48 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 30FEC1858320; Thu, 4 Mar 2010 11:59:48 -0500 (EST) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id F0B761858267 for ; Thu, 4 Mar 2010 11:59:34 -0500 (EST) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1NnEOc-0003RR-JJ for sup-talk@rubyforge.org; Thu, 04 Mar 2010 11:59:34 -0500 From: Rich Lane To: sup-talk In-reply-to: <1267702902-sup-4834@tihlde.org> References: <1267478622-sup-2939@tangerine.lanl.gov> <1267654880-sup-4875@zyrg.net> <1267702902-sup-4834@tihlde.org> Date: Thu, 04 Mar 2010 11:59:34 -0500 Message-Id: <1267720861-sup-759@zyrg.net> User-Agent: Sup/git Subject: Re: [sup-talk] sup install error X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Helge Titlestad's message of 2010-03-04 06:45:04 -0500: > Excerpts from Rich Lane's message of Wed Mar 03 23:23:06 +0100 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? > > If this breaks UTF-8 support more, I humbly vote against. UTF-8 with ncursesw > might not be the perfect solution, but it seems to be the only solution at the > moment, and anyone outside stricy ascii-writing countries will expect it to > Just Work[tm]. I committed a patch to master that switches the gem dependency to plain ncurses. I'd rather have all users be able to install than having utf8 support by default, especially when the way to enable utf8 is so easy - gem install ncursesw. I've promoted the debug log about missing ncursesw to an info log. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk