Padraig O'Briain writes: > I have spoken to Laca about this and RE's policy is to always deliver > the include files for a library.
I think the wires are getting crossed somewhere, because the fact that it's a library alone does not trigger the need to deliver anything other than the .so.1 file. The actual policy is here: http://www.opensolaris.org/os/community/arc/policies/libraries/ See W3. (It's also somewhere on sac.sfbay ... but that system is dead right now.) The key issue is whether this is intended to be private or not. > 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. No, that's not the only option. They can also download the source themselves and compile a new version of the library, and use that _instead_. Mixing and matching header files and other bits related to an undocumented library would indeed be a bad idea, but it's certainly not the only option if the library is private. > So interface classification should be Volatile. OK. That works. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
