On Fri, Apr 20, 2012 at 8:14 PM, Antonio Terceiro <[email protected]> wrote: > Per Andersson escreveu isso aí: >> On Sun, Apr 15, 2012 at 5:38 PM, Per Andersson <[email protected]> wrote: >> > On Sun, Apr 15, 2012 at 1:24 PM, Antonio Terceiro <[email protected]> >> > wrote: >> >> >> >> If ruby-ncursesw supports everything that ruby-ncurses supports, than I >> >> think we should go fo it. Since ruby-ncurses has few reverse >> >> dependencies, it should be ok. Could you please also test tpp (the other >> >> rdep besides sup-mail) with ruby-ncursesw? >> > >> > I'll have a look at that. >> >> The examples shipped with tpp works fine with ruby 1.8 and ruby-ncursesw >> instead of libncurses-ruby1.8. >> >> With ruby 1.9.1 it fails to read keyboard input from the user. > > That only happens with ruby-ncursesw, or does it also happen with the > regular ruby-ncurses?
With the compat patch for STR2CSTR applied for ruby-ncurses (necessary in order to compile for Ruby >= 1.9.0) it shows the exact same behaviour as ruby-ncursesw. I think ruby-ncursesw should also provide ruby-ncurses. How should that transition work exactly? I asked in #debian-mentors and the transitional packages from ruby-ncurses (which are now in squeeze) should be dropped. What about the transition from ruby-ncurses to ruby-ncursesw? Should ruby-ncursesw just provide ruby-ncurses or should there be a also be conflicts in there? From what I can tell ruby-ncursesw should provide ruby-ncurses and conflict ruby-ncurses (if that is at all possible). -- Per > -- > Antonio Terceiro <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/cabyrxst+5dyrmvnzrg+o6zgwdqxxm-ab7vep+bhk_4eg0q6...@mail.gmail.com
