Thanks, most of the updates look good. A few more comments: > This is test programs that comes with the standard distribution, but > they are not necessary to run the MySQL server and other binaries. > They are necessary to ensure that our way of building MySQL does not > break any functionality.
So these are only for build testing (the typical 'make test' cycle)? If yes, is there really a reason to package them? Or are they useful for end users? > It is the MySQL server binary. The interface should maybe be the "server > program command line options" ? How do I pass those command line options when starting via smf? If these are needed, they probably need to be smf properties? Or can they be in config file? > ok, error codes should be Commited interface while the messages can > change as you say, so they should be UnCommited. So scripts should rely > on the errorcodes and not messages. Should both be listed here as > interfaces? Note that Uncommitted is also a relatively stable public interface type. Volatile is closer if the messages can change, but if scripts should not rely on the exact message text anyway, it is "Not-an-interface". For more background see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
