Log message:
Don't hardcode PID file. Instead, give the user the option to set it. The
rc.d script overrides my.cnf directives. Hardcoding the PID can cause a
problem on systems transitioning to MySQL packages from pkgsrc.

Log message:
Fix SMF_METHOD_FILE expansion.

Log message:
Import initial SMF support for individual packages.

Log message:
Remove example rc.d scripts from PLISTs.

These are now handled dynamically if INIT_SYSTEM is set to "rc.d", or
ignored otherwise.

Log message:
Recursive PKGREVISION bump for OpenSSL API version bump.

Log message:
Remove CONFLICTS with ${PKGBASE}, these are automatic.

Avoids unnecessary pkgin warning.

Log message:
Changes 5.1.72:
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly \ 
prepare to compare a NULL column prefix in a secondary index with a non-NULL \ 
column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a \ 
delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing \ 
the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an \ 
assertion failure. The assertion has been modified to allow NULL BLOB pointers \ 
if an error occurs during a BLOB write.
* InnoDB: The srv_master_thread background thread, which monitors server \ 
activity and performs activities such as page flushing when the server is \ 
inactive or in a shutdown state, runs on a one second delay loop. \ 
srv_master_thread would fail to check if the server is in a shutdown state \ 
before sleeping.
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling \ 
compressed-only pages.
* Within a stored program, comparison of the value of a scalar subquery with an \ 
IN clause resulted in an error for the first execution and raised an assertion \ 
for the second execution.
* The my_strtoll10() function could incorrectly convert some long string-format \ 
numbers to numeric values and fail to set the overflow flag.
* For queries that accessed an INFORMATION_SCHEMA table in a subquery, and \ 
attempt to lock a mutex that had already been locked could cause a server crash.
* For DIV expressions, assignment of the result to multiple variables could \ 
cause a server crash.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded \ 
because the deprecated OPTION keyword has been removed from SET syntax.
* If one connection changed its default database and simultaneously another \ 
connection executed SHOW PROCESSLIST, the second connection could access invalid \ 
memory when attempting to display the first connection's default database. \ 
memory.

Log message:
don't use gethostbyname_r unless there is a prototype in scope.

Log message:
Changes 5.1.71:

Functionality Added or Changed
* comp_err now checks to make sure that new errors are not being added to MySQL \ 
5.1 or 5.5 because the set of errors for these series is frozen.

Bugs Fixed
* InnoDB: During an insert buffer merge, InnoDB would invoke \ 
lock_rec_restore_from_page_infimum() on a potentially invalid record pointer.
* InnoDB: The page_zip_validate() consistency check would fail after compressing \ 
a page, in page_zip_compress(). This problem was caused by \ 
page_zip_decompress(), which would fail to set heap_no correctly when a record \ 
contained no user data bytes. A record with no user data bytes occurs when, for \ 
example, a primary key is an empty string and all secondary index fields are \ 
NULL or an empty string.
* InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never \ 
used, has been removed from the code base.
* Partitioning: When dropping a partitioned table, the table's .par file was \ 
deleted first, before the table definition or data. This meant that, if the \ 
server failed during the drop operation, the table could be left in an \ 
inconsistent state in which it could neither be accessed nor dropped.
* Shared-compatibility conflict errors occurred for RPM install operations, even \ 
if no shared-compatibility RPMs were already installed.
* A user variable referenced during execution of a prepared statement is set to \ 
memory that is freed at the end of execution. A second execution of the \ 
statement could result in Valgrind warnings when accessing this memory.
* Misoptimization of left expressions in prepared statements could cause a \ 
server exit.
* Subsequent to Prepared statement needs to be re-prepared errors, inserts into \ 
DECIMAL columns caused a server exit.
* Assigning the result of a subquery to a user variable raised an assertion when \ 
the outer query included DISTINCT and GROUP BY.

Log message:
* .include "../../devel/readline/buildlink3.mk" with USE_GNU_READLINE=yes
  are replaced with .include "../../devel/readline/buildlink3.mk", and
  USE_GNU_READLINE are removed,

* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
  are replaced with .include "../../mk/readline.buildlink3.mk".