From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs40143fga; Fri, 12 Feb 2010 19:13:08 -0800 (PST) Received: by 10.224.73.76 with SMTP id p12mr1102740qaj.187.1266030787372; Fri, 12 Feb 2010 19:13:07 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 26si11276193qwa.2.2010.02.12.19.13.06; Fri, 12 Feb 2010 19:13:07 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 9ACC0158807C; Fri, 12 Feb 2010 22:13:06 -0500 (EST) X-Greylist: delayed 336 seconds by postgrey-1.31 at rubyforge.org; Fri, 12 Feb 2010 22:12:11 EST Received: from mail-bw0-f215.google.com (mail-bw0-f215.google.com [209.85.218.215]) by rubyforge.org (Postfix) with ESMTP id 8EAA3158806F for ; Fri, 12 Feb 2010 22:12:11 -0500 (EST) Received: by bwz7 with SMTP id 7so2659112bwz.26 for ; Fri, 12 Feb 2010 19:12:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=TQ24Sh5Aqqb0947lA0nD1CUw2wqwXuj43ukG93TVLEA=; b=FLK+LA0o22AmZA1oROXjxvsBzh+edXnrYWtNjfQSuO7mJqsrKZIAPAGjx8/QJM3NSB plRgNHIydV/e9XSo/U2o9RNEjfWoGywDUTYaCN4Li5F+a/erboVuOl12Tpg3SidWWj8g Ino/FisV5BC0bOZJhmNvJXkbBP0T6aY8vV0XU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xQkvwZk7onDA8YiqMr9IEPmxUkX5V3xR9mnnJkajGhKOEZ+5ysLKn4U25Cm6Ia8/G/ Y5tO65gXN/OvENF/0b9VREBYjKdfJ1RNcnk9RRGSt1spZ/DZZylH7KXod+e+CEu4sOjJ fRycII7yuuv1pHYsYLTWWOF2UkfaJfqJB4QU0= MIME-Version: 1.0 Received: by 10.204.151.91 with SMTP id b27mr1382888bkw.110.1266030390957; Fri, 12 Feb 2010 19:06:30 -0800 (PST) Date: Fri, 12 Feb 2010 22:06:30 -0500 Message-ID: <80055d7c1002121906t6e6cbe6cpf6188ddde6e82d3e@mail.gmail.com> From: Andrei Thorp To: sup-talk@rubyforge.org Subject: [sup-talk] Ruby Ncurses Bindings 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hello, For several versions now, sup has shipped with ncurses bindings for ruby. I don't understand why they're in there. For my Arch package, I delete the ncurses.rb file and allow Sup to use the system-installed ruby ncurses bindings instead. Funny enough, they work properly in Arch whereas the provided bindings don't. Is there any reason to have the bindings in there? Other distros? Anyway, I have no problems continuing to delete them if there is a reason. Cheers, -Andrei "Garoth" Thorp _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk