Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
It's only really needed on Darwin but building there on all platforms
allows us to keep the same PLIST for all of them: buildling the backend
results in two more include files to be installed.
Per discussion with recht@ our dedicated postgresql74-* MAINTAINER ;)
|
|
|
|
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
|
|
before copying files over, to avoid accidental overwrite of the config
file via the stale symlink
|
|
it is still on by default to preserve compatibility (use option "-bdb" to
disable).
While here, fix typo in CONFIGURE_ARGS that had caused the dnssrv backend
not to build; bump PKGREVISION.
|
|
* Make mysql4-client build on NetBSD 1.[56]*
* Don't install mysqld and friends in mysql4-client (eww!)
* Remove an unneeded patch.
* Remove duplicated files in mysql4-client's PLIST.
Also, use assembler functions when MACHINE_ARCH == i386.
This closes PR pkg/27154, pkg/27720, pkg/27744 and pkg/28035.
BTW, I tested them on NetBSD 1.6.2, 2.0_RC4 and -current.
Bump PKGREVISION for both packages.
|
|
|
|
|
|
p5-Lingua-EN-Inflect
p5-UNIVERSAL-moniker
p5-Class-DBI
|
|
Class::DBI provides a convenient abstraction layer to a database.
It not only provides a simple database to object mapping layer, but can
be used to implement several higher order database functions (triggers,
referential integrity, cascading delete etc.), at the application level,
rather than at the database.
This is particularly useful when using a database which doesn't support
these (such as MySQL), or when you would like your code to be portable
across multiple databases which might implement these things in
different ways.
In short, Class::DBI aims to make it simple to introduce 'best practice'
when dealing with data stored in a relational database.
|
|
only UI changes according to release announcements.
While here, introduce some package changes:
* handle config.inc.php via CONF_FILES mechanism instead of PLIST magick,
the symlink config.inc.php -> ${PKG_SYSCONFDIR}/config.inc.php is now
included in PLIST
* use NO_BUILD, NO_CONFIGURE
* Apache config fragment file is now installed as ${EXDIR}/apache.conf, not
copied to ${PKG_SYSCONFDIR} and MESSAGE points to the ${EXDIR} location
* do not install any *.sh files - they are developer stuff only
* use INSTALL_DATA for all files except scripts/convertcfg.pl
|
|
databases/p5-DBIx-ContextualFetch
databases/p5-Ima-DBI
devel/p5-Class-WhiteHole
www/p5-Apache-AuthCookie
www/p5-Apache-Session-Wrapper
www/p5-MasonX-Request-WithApacheSession
|
|
Ima::DBI attempts to organize and facilitate caching and more
efficient use of database connections and statement handles.
One of the things I always found annoying about writing large
programs with DBI was making sure that I didn't have duplicate
database handles open. I was also annoyed by the somewhat wasteful
nature of the prepare/execute/finish route I'd tend to go through
in my subroutines. The new DBI->connect_cached and DBI->prepare_cached
helped alot, but I still had to throw around global datasource,
username and password information.
So, after a while I grew a small library of DBI helper routines
and techniques. Ima::DBI is the culmination of all this, put into
a nice(?), clean(?) class to be inherited from.
|
|
It always struck me odd that DBI didn't take much advantage of Perl's
context sensitivity. DBIx::ContextualFetch redefines some of the various
fetch methods to fix this oversight. It also adds a few new methods for
convenience (though not necessarily efficiency).
|
|
setting now, do so for aesthetic reasons
|
|
for both PHP 4.x and 5.x.
|
|
to include "../../lang/php/ext.mk" after extension CONFIGURE_ARGS
setting; successful build confirmed with both PHP 4.x and PHP 5.x
|
|
|
|
|
|
|
|
|
|
includes support for more advanced features such as prepared statements.
|
|
with this patch.
|
|
buildlink3.mk files
|
|
some of the patches disable part of the build and break the client
build.
should fix build issue noted on tech-pkg.
|
|
leave the DEPENDS in a form which allows PHP 5.x to match, since it should
work just as well
|
|
PHP-enabled
bump PKGREVISION
|
|
|
|
|
|
|
|
PHP5 too
|
|
lang/php/ext.mk before setting CONFIGURE_ARGS
|
|
individual PHP extension packages with either PHP 4.x or PHP 5.x
convert existing php4-* packages to this framework and import as php-*
|
|
|
|
built and installed.
bump PKGREVISION.
|
|
|
|
patches here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not ""../../databases/mysql4-client" because the later is a newer version.
|
|
so that we'd not force dependance on specific MySQL version, and instead pick
the currently installed mysql*-client (or install the default if there
is no mysql-client package installed yet)
this makes package buildable with arbitrary MySQL version, such as 3.23.x,
4.0.x or 4.1.x
|
|
|
|
|
|
|