Hi, Danek Duvall wrote: > Hi. Mike asked me about the way that ncurses was delivering onto the > system, and mentioned that while the headers were being delivered into > /usr/include, the libraries were being delivered into /usr/gnu/lib. That > sounded odd to me, so I came back and checked, and, unfortunately, the spec > is conflicted over this. > > Is there any ARC policy about this? There are no files delivered /usr/gnu/include ever before.
> In the text, > > >> Because most the binaries and libraries use same name with SVR4 curses, >> we ship the binaries in /usr/gnu/bin and the libraries in >> /usr/lib/libncurses. >> > > It should be /usr/gnu/lib. We changed the target directory several times. This place should be corrected. > you say the libraries go in /usr/lib, while in the interface table, > > >> /usr/gnu/lib/libncurses.so.5 >> /usr/gnu/lib/libform.so.5 >> /usr/gnu/lib/libmenu.so.5 >> /usr/gnu/lib/libpanel.so.5 >> Uncommitted Supporting libraries >> > > you say they go in /usr/gnu/lib. > > I'm sorry for not noticing that when the case was still running, but it'd > be good to have some clarification on the issue. > > >> /usr/include/ncurses/curses.h >> > > I'll also note that the build 100 delivery appears to put the header files > directly in /usr/include, not in /usr/include/ncurses, which means they > overwrite files already delivered in SUNWhea, through the OS/Net > consolidation. > > >> /usr/gnu/bin/ncurses5-config >> Uncommitted CLI binaries. >> > > And while I'm here and thinking about these things (sorry), this probably > ought to go in /usr/bin so that it can be found, even though the curses > libs are buried out of the way. > > Maybe you are right. How about adding a link /usr/bin/ncurses5-config->/usr/gnu/bin/ncurses5-config? > Thanks, > Danek >
