I have spoken to Laca about this and RE's policy is to always deliver the include files for a library.
Someone might want to build or develop a 3rd party app that uses libdaemon. If we don't ship the headers, the only option they have is find the same version that is shipped with Solaris and extract the headers for themselves. Worse, if they pick the latest version and they to use those headers with the old library there is likely to be problems. So interface classification should be Volatile. Padraig Padraig O'Briain wrote: > It is my intention that libdaemon.so should be Private. > > The library name is actually libdaemon.so.0.3.0. > This was an error on my part. > > Padraig > > James Carlson wrote: >> Brian Cameron writes: >> >>> My understanding of Sun manpage policy is that all libraries >>> should have manpages, if only to describe that they are Uncommitted >>> in the ATTRIBUTES section and not to be used. >>> >> >> No, if it's intended as "Private," as this one seems to be, then *by >> definition* it must not have man pages. >> >> In that case, it should be shipped as libdaemon.so.1 (not >> libdaemon.so, as the case materials seem to have), and it should omit >> any compilation symlink and associated header files. >> >> If it's meant to be used by multiple projects, and not just this one, >> then it may well need a much closer look and higher commitment, which >> would require a man page. >> >> >
