Commit graph

24 commits

Author SHA1 Message Date
wiz
3184463075 Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
2012-10-03 21:53:53 +00:00
asau
ba25df56c6 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-02 21:25:15 +00:00
obache
cfbdbc01b7 Revision bump after updating perl5 to 5.14.1. 2011-08-14 08:18:04 +00:00
seb
febfbb41f9 Bump the PKGREVISION for all packages which depend directly on perl,
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-21 16:32:42 +00:00
obache
84e09b4531 Update HOMEPAGE location. 2010-08-06 04:51:23 +00:00
obache
de7ed8be51 Update p5-tokyotyrant to 1.16. 2010-01-17 02:53:28 +00:00
obache
122ffd0637 TokyoCabinet related HOMEPAGEs have been moved. 2009-11-25 11:33:55 +00:00
obache
850b462b9c Update p5-tokyotyrant to 1.14. 2009-07-21 11:33:31 +00:00
obache
54341d51d0 Update p5-tokyotyrant to 1.13. 2009-07-07 11:43:01 +00:00
joerg
61b9e83a85 Remove @dirrm entries from PLISTs 2009-06-14 17:38:38 +00:00
obache
b94c64048d Update tokyotyrant-perl to 1.12. 2009-06-05 12:07:05 +00:00
obache
981578bd84 Update tokyotyrant to 1.1.27.
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-24 12:42:44 +00:00
wiz
6ac11147ab Use standard location for LICENSE line (in MAINTAINER/HOMEPAGE/COMMENT
block). Uncomment some commented out LICENSE lines while here.
2009-05-19 08:59:00 +00:00
obache
6396473d75 Update tokyotyrant-perl to 1.10, for new tokyotyrant protocol. 2009-05-07 11:06:28 +00:00
obache
d25289ed5b Update p5-tokyotyrant to 1.8, for tokyotyrant-1.1.17. 2009-03-21 05:37:46 +00:00
obache
6af05c81cd No need DIST_SUBDIR anymore. 2009-02-15 12:42:57 +00:00
obache
c221dc4f45 Update p5-tokyotyrant to 1.7, for tokyotyrant-1.1.15. 2009-02-15 09:03:46 +00:00
obache
f594754c83 distfile was replaced silently (some document was changed).
bump PKGREVISION.
2009-02-12 15:33:58 +00:00
obache
8b4b6a342d Update p5-tokyotyrant to 1.6, for tokyotyrant-1.1.14. 2009-02-12 12:31:52 +00:00
obache
452cd17302 Update p5-tokyotyrant to 1.5, for tokyotyrant-1.1.12. 2009-02-07 08:25:20 +00:00
obache
a339e95d0e Update p5-tokyotyrant to 1.4, for tokyotyrant-1.1.10. 2009-01-04 11:05:29 +00:00
obache
c556efa53d Update p5-tokyotyrant to 1.3, for tokyotyrant-1.1.9. 2008-12-07 11:36:24 +00:00
obache
d738e1081e Fixes perl5 path in test scripts. 2008-11-26 17:06:05 +00:00
obache
dcf6723f5e Import p5-tokyotyrant-1.2 as databases/p5-tokyotyrant.
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.
2008-10-26 11:40:33 +00:00