Age | Commit message (Collapse) | Author | Files | Lines |
|
1) they will not be maintained anymore
2) their package directory names where confusing (mysql4-* have a more
recent version)
These package directories may be used for meta-pkgs in the future (pulling
in the latest mysql?-* packages).
|
|
|
|
CONFIGURE_ARGS.
|
|
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|
|
--enable-assembler supplied.
|
|
the symbol naming is wrong, so no --enable-assembler will get it built.)
|
|
Functionality added or changed:
* Added the mysql_get_client_version C API function to the embedded
server library. (It was present in the regular client library but
inadvertently omitted from the embedded library.)
Please see http://dev.mysql.com/doc/mysql/en/news-4-0-26.html
for more information.
|
|
The ABI didn't change and the vulnerability is server side-only.
|
|
the following vulnerabilities:
http://www.appsecinc.com/resources/alerts/mysql/2005-001.html
http://www.appsecinc.com/resources/alerts/mysql/2005-002.html
Please see changelog: http://dev.mysql.com/doc/mysql/en/news-4-0-25.html
|
|
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
|
|
include dir is automatically available in ${CPPFLAGS}, following
the example of postgres74-lib.
|
|
|
|
noted by Pierre Bourgin on tech-pkg@
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
portable shell constructs.
|
|
which can take multiple values -- "pax" or "gtar". The default value
of EXTRACT_USING is "pax", which more closely matches reality since
before, we were using bootstrap "tar" for ${GTAR} and it was actually
pax-as-tar. Also, stop pretending pax-as-tar from the bootstrap kit
or on NetBSD is GNU tar. Lastly, in bsd.pkg.extract.mk, note whether
we need "pax" or "gtar" depending on what we need to extract the
distfiles.
|
|
|
|
http://www.k-otik.com/english/advisories/2005/0252
See http://dev.mysql.com/doc/mysql/en/news-4-0-24.html
Bumped BUILDLINK_RECOMMENDED to 4.0.24.
|
|
|
|
See http://dev.mysql.com/doc/mysql/en/News-4.0.23.html for the full
list of changes.
This update applies the fix for the mysqlaccess script symlink
vulnerability, bump BUILDLINK_RECOMMENDED.
|
|
may contain a wrong path to the perl executable.
|
|
|
|
mysql*-client! explain which are the required packages to run the script.
|
|
script.
Bump PKGREVISION to each package respectively.
|
|
that use pthreads already implement their own probes for pthreads, so
we don't need to auto-add the compiler/linker flags.
|
|
* Use PTHREAD_AUTO_VARS=no to disable linking to libpthread all programs
and libraries, which is wrong.
* Set USE_LIBTOOL and GNU_CONFIGURE before including bsd.prefs.mk, so
the test for _OPSYS_MAX_CMDLEN is not skipped.
Bump PKGREVISION to each package respectively
(mysql-client and mysql4-client), closes PR pkg/28162 and PR pkg/28222.
|
|
|
|
|
|
|
|
Bump package revision because of this changes. This fixes PR pkg/28313
by Jarle Greipsland.
|
|
|
|
mysql_drop_db(), mysql_create_db() and mysql_connect(), required
to build some applications using the MySQL 3.23.x API.
|
|
Functionality added or changed:
* The --with-openssl option for configure now accepts a path
prefix as an argument. --with-openssl-includes and
--with-openssl-libs are still supported, but are needed only
to override the default values. (Bug #5494)
* Added new --without-man option to configure to suppress
building/installing the manual pages. (Bug #5379)
* InnoDB: New mysqld option --innodb-table-locks and session
variable innodb_table_locks (on by default). In applications
using AUTOCOMMIT=1, InnoDB's internal table locks can cause
deadlocks. You can set innodb_table_locks=0 in `my.cnf' to
remove that problem. See section 16.17 Restrictions on InnoDB
Tables. (Bug #3299, Bug #5998)
* InnoDB: Added the startup option and settable global variable
innodb_max_purge_lag for delaying INSERT, UPDATE and DELETE
operations when the purge operations are lagging. The default
value of this parameter is zero, meaning that there will not be
any delays. See section 16.13 Implementation of Multi-Versioning.
* InnoDB: Change error code to HA_ERR_ROW_IS_REFERENCED if we
cannot DROP a parent table because it is referenced by a FOREIGN
KEY constraint.
And a lot of bugfixes: http://dev.mysql.com/doc/mysql/en/News-4.0.22.html
|
|
|
|
|
|
|
|
|
|
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
|
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
|
|
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
|
|
|
|
|
|
|
|
for "compress" and "uncompress". Convert to bl3 to fix build.
|
|
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
|
|
|
|
|