David.Comay at sun.com wrote: >> 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. > > Is there a reason you're using Volatile rather than Uncommitted? The > latter would not allow incompatible versions changes in a patch while > allowing the library to evolve during the creation of a minor release. > > Or is libdaemon really so unstable that Volatile makes more sense? As per the taxonomy examples, Volatile is rather useless as level for libraries.
There seems to be two possibilities. I thought the project was headed towards "Project Private". It seems to have morphed into something Public. If it is some type of Public, it needs to be documented. Perhaps I missed something in the mail trail.... - jek3
