Nicolas Williams writes: > I think that's a track record that speaks for itself. > > Also, some parts of the API are deprecated and some are experimental. > The API docs (which aren't manpages, BTW), are clear about the stability > attributes of the various interfaces.
In that case, we should make our stability attributes match the ones advertised by the software authors. Use "Uncommitted" or better for the things that are in fact stable, and "Volatile" and "Obsolete" for the experimental and deprecated parts. Just pass the upstream guarantees to the downstream users. I don't see a good reason to make things hard on future projects that might want to use these interfaces by making a lesser promise to Solaris users than the software author does. (It doesn't matter whether the documentation is in man page format, so I'm not sure I understand your parenthetic comment. Care to elaborate?) > I don't think using Volatile does that. Using Uncommitted might > encourage more third-parties to use the SQLite shipped in Solaris. From > a making-Solaris-easier-to-develop-on that seems to me like the right > thing to do. I certainly agree with that. > BTW, the filesystem locations of the CLI, header and compilation link > ought to be Committed. Same with the static linking archive, if we do > ship it. Indeed. The interfaces table is unclear. I *think* what was actually meant was that the interfaces provided by the CLI are Volatile, and not that the file system path itself was. But I can't tell. :-/ -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
