http://wikis.sun.com/display/WebStack/MySQL50ArcCase

> Including MySQL 5.0 with Solaris - DRAFT
> 
> 17 October 2007



>     2.6 Configuration and Enviroment settings.

As which user will it be defined to run as?

(Since it reads ~/.my.cnf, this seems like a good section to cover
that info.)



> 3.  Core Modules
> 
>     The MySQL server has several storage engines built in
>     (specified when you create tables), the primary ones are:
>        InnoDB - ACID storage engine
>        MyIsam - non-ACID storage engine
>        Other engines exists, see mysql.org[1] for details, where
>        we will include the engines as the standard distribution.

The last part of the sentence there is confusingly worded IMO.
I think you mean that all of the built-in storage engines will
be included in the build delivered by this case?

Also, the section is titled "Core Modules" but talks only about
storage engines. Leads to the question, are there any other kind of
core modules beside the storage engines?


> 6. Packaging and Delivery
> 
>     We propose to package MySQL under the following packages:
> 
>          SUNWmysql50 - Server package (including server deamon, C API,
>                      man pages, I18N)

For sfw you need to deliver usr and root packages so you'll need at
least SUNWmysql50r and SUNWmysql50u.

(Look around in the sources under src/pkgdefs/* for examples.)

>          SUNWmysql50test - MySQL test packages

Aside from the file path mentioned in s2.5 and the package name above,
this doc doesn't say anything about this test suite. What does it do,
why does it need to be shipped with the server? Add a section that
covers this topic.


>     7.3.    Exported Interfaces

The smf info is not listed, that's also an exported interface, please
add.


>     NAME                      STABILITY       NOTES
> 
>     MySQL Server              Committed       Server deamon program

As I mentioned last time, this is not very clear. What is the case
exporting here?

A useful way to think about exported interfaces is to picture you are
writing script or code which interacts with the system somehow,
document those points of interaction.

Not clear how my hypothetical script interacts with "Server deamon
program"?

>     MySQL Server config file  Committed       Config file

Config file syntax or location?

>     Error messages            Committed       I18N Translated Error codes.

Can you clarify on these? Codes (i.e. numeric error codes) or
human-readable messages?

If the latter, messages are not usually Committed. That would mean
the words will never change, so it is not possible to reword the
message to be clearer nor to fix a spelling mistake or anything,
because it is ok for customers to write scripts which grep for the
exact string of the message.

Message text is typically "Not-an-interface", see
http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/

Given that, are these error messages really Committed? I'm not saying
they can't be, if that's how the MySQL development community treats
them, only want to reconfirm since it is unusual.



> ================================================================
> Addendum 1:       MySQL Integration Directory and File Structure.

Please also list the soft links in the file listing.


thanks...

-- 
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems

Reply via email to