On Tue, Sep 18, 2012 at 3:52 PM, Dr. Werner Fink <werner@suse.de> wrote:
Hmmm ... I'm not aware that README.devel is that low level. Things like
LIBS="$(ncursesw5-config --libs)" CFLAGS="$(ncursesw5-config --cflags)" export LIBS CFLAGS
shouldn't that low level. The reason of having 4 ncurses config scripts is simply that there are still applications without wide character support. For this I've done ncurses5-config and ncurses6-config, for all others the ncursesw5-config and ncursesw6-config are usefull.
The ncurses6-config and ncursesw6-config are the upcoming new ABI which includes experimental mouse version 2 supports wheel mice with buttons 4 and 5. The experimental extended colors allows encoding of 256 foreground and background colors, e.g., with the xterm-256color or xterm-88color terminfo entries. This requires ABI 6 because it changes the size of cchar_t. Beside this ABI 6 will provide full reentrant support as well as extend pthread support.
All four versions are binary incompatible otherwise I would not provide four version of libncurses nor four include paths. OK I could also support only one ncurses version like ncursesw5 to allow developers not to read README.devel but this would intend that e.g. YaST2 ncurses GUI would loose reentrant and pthread safe ncurses support.
Werner
Hi, Werner, Thanks for explanation. In this case it's presage upstream to blame...who seems to "hard-code" curses which make ncurses not possible. To change configure.ac will work. Now I had the basic knowledge of our 4 versions of ncurses (You're a good teacher, last time it was freetype2), but...err...actually knowing why doesn't mean knowing how. eg: I know the difference between the libraries, but I still don't know which one presage used, that's what blocks me from "choosing" which lib to use...so everytime I face ncurses , I have to launch a saturation attack... Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org