summaryrefslogtreecommitdiff
path: root/databases/p5-tokyotyrant
AgeCommit message (Collapse)AuthorFilesLines
2016-07-10Fixed pkglint warning. Bumped revision.rillig1-3/+3
2016-07-09Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.wiz1-2/+2
2016-06-08Bump PKGREVISION for perl-5.24.wiz1-2/+2
2015-11-03Add SHA512 digests for distfiles for databases categoryagc1-1/+2
Problems found with existing distfiles: distfiles/D6.data.ros.gz distfiles/cstore0.2.tar.gz distfiles/data4.tar.gz distfiles/sphinx-2.2.7-release.tar.gz No changes made to the cstore or mariadb55-client distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-06-12Recursive PKGREVISION bump for all packages mentioning 'perl',wiz1-2/+2
having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2015-03-15Set MAINTAINER to pkgsrc-users.hiramatsu1-2/+2
2014-05-29Bump for perl-5.20.0.wiz1-2/+2
Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
2013-05-31Bump all packages for perl-5.18, thatwiz1-2/+2
a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints.
2012-10-03Bump all packages that use perl, or depend on a p5-* package, orwiz1-2/+2
are called p5-*. I hope that's all of them.
2012-10-02Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-3/+1
2011-08-14Revision bump after updating perl5 to 5.14.1.obache1-2/+2
2010-08-21Bump the PKGREVISION for all packages which depend directly on perl,seb1-1/+2
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1. The list of packages is computed by finding all packages which end up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl, or PERL5_PACKLIST defined in their make setup (tested via "make show-vars VARNAMES=..."), minus the packages updated after the perl package update. sno@ was right after all, obache@ kindly asked and he@ led the way. Thanks!
2010-08-06Update HOMEPAGE location.obache1-2/+2
2010-01-17Update p5-tokyotyrant to 1.16.obache2-7/+7
2009-11-25TokyoCabinet related HOMEPAGEs have been moved.obache1-2/+2
2009-07-21Update p5-tokyotyrant to 1.14.obache2-6/+6
2009-07-07Update p5-tokyotyrant to 1.13.obache2-6/+6
2009-06-14Remove @dirrm entries from PLISTsjoerg1-2/+1
2009-06-05Update tokyotyrant-perl to 1.12.obache2-6/+6
2009-05-24Update tokyotyrant to 1.1.27.obache2-6/+6
Changes: 2009-05-11 Mikio Hirabayashi <mikio@users.sourceforge.net> * tcrtest.c (runtable, proctable): "-exp" option was added. * ttskelnull.c: new file. * tokyotyrant.idl: new file. - Release: 1.1.27
2009-05-19Use standard location for LICENSE line (in MAINTAINER/HOMEPAGE/COMMENTwiz1-2/+1
block). Uncomment some commented out LICENSE lines while here.
2009-05-07Update tokyotyrant-perl to 1.10, for new tokyotyrant protocol.obache2-6/+8
2009-03-21Update p5-tokyotyrant to 1.8, for tokyotyrant-1.1.17.obache2-6/+6
2009-02-15No need DIST_SUBDIR anymore.obache2-6/+5
2009-02-15Update p5-tokyotyrant to 1.7, for tokyotyrant-1.1.15.obache2-7/+6
2009-02-12distfile was replaced silently (some document was changed).obache2-5/+7
bump PKGREVISION.
2009-02-12Update p5-tokyotyrant to 1.6, for tokyotyrant-1.1.14.obache2-6/+6
2009-02-07Update p5-tokyotyrant to 1.5, for tokyotyrant-1.1.12.obache2-6/+6
2009-01-04Update p5-tokyotyrant to 1.4, for tokyotyrant-1.1.10.obache2-6/+6
2008-12-07Update p5-tokyotyrant to 1.3, for tokyotyrant-1.1.9.obache2-6/+6
2008-11-26Fixes perl5 path in test scripts.obache1-1/+3
2008-10-26Import p5-tokyotyrant-1.2 as databases/p5-tokyotyrant.obache4-0/+51
This module implements the pure Perl client which connects to the server of Tokyo Tyrant and speaks its original binary protocol. Tokyo Tyrant is a package of network interface to the DBM called Tokyo Cabinet. Though the DBM has high performance, you might bother in case that multiple processes share the same database, or remote processes access the database. Thus, Tokyo Tyrant is provided for concurrent and remote connections to Tokyo Cabinet. It is composed of the server process managing a database and its access library for client applications. The server can embed Lua, a lightweight script language so that you can define arbitrary operations of the database. The server features high concurrency due to thread-pool modeled implementation and the epoll/kqueue mechanism of the modern Linux/*BSD kernel. The server and its clients communicate with each other by simple binary protocol on TCP/IP. Protocols compatible with memcached and HTTP/1.1 are also supported so that almost all principal platforms and programming languages can use Tokyo Tyrant. High availability and high integrity are also featured due to such mechanisms as hot backup, update logging, and replication.