On Fri, 2006-11-10 at 15:02 +0100, Fabian Groffen wrote: > In the ebuild I sticked this when the ncurses USE-flag is enabled. When > it is not (the default) then you only get --disable-slang, meaning you > apparently want curses from wherever that comes. So what is the desired > behaviour here? It's not entirely clear what it should be. I get the > impression you only want to overwrite if you want ncurses. My nano, > which was built without this USE-flag, does link against libncursesw. > Also when I build with ncurses USE-flag.
Huh, did not consider the use flags. It makes some sense to "--enable-overwrite" with enabled use-flag 'ncurses' only. > > Is there curses available on Solaris by default? Isn't it then a good > idea to add ncurses to the default flags of the solaris profile? Did > you use the USE-flag when compiling? curses is installed here, but I'm not the admin of this machine. IMO it _is_ installed by default. What is the difference between "--enable-overwrite" and adding it to the default flags (you mean CPPFLAGS in profile.bashrc ?) ? Hmm, I neither had 'ncurses' nor 'slang' use-flag set, but nano links against ncurses if configure-check for "-lncurses" works. Maybe nano is broken here ? I have seen other packages checking for "ncurses/ncurses.h", nano does not do this. Why do we need nano on solaris at all ? OTOH: Bash unconditionally depends on ncurses, so we always have it installed. Why not enable 'ncurses' useflag in solaris profile ? I expect much less problems with "--enable-overwrite" and 'ncurses' useflag enabled - like that one in nano. /haubi/ -- Michael Haubenwallner SALOMON Automation GmbH Forschung & Entwicklung A-8114 Friesach bei Graz mailto:[EMAIL PROTECTED] http://www.salomon.at No HTML/MIME please, see http://expita.com/nomime.html -- [EMAIL PROTECTED] mailing list
