summaryrefslogtreecommitdiff
path: root/chat/i2cbd
AgeCommit message (Collapse)AuthorFilesLines
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 onesagc1-1/+2
2005-02-22Might as well be MAINTAINER for i2cb{,d}. Thanks for making these, hubert!jwise1-2/+2
2005-02-21Sign over maintainership to tech-pkg@hubertf1-2/+2
2004-12-30Make this package build on NetBSD-current by casting arguments to ctypeagc4-2/+40
macros where necessary. Bump package revision.
2004-04-11Convert to buildlink3.snj1-2/+2
2003-10-24A new BETA is out, i2cbd-2.0_BETA1. Update pkg accordingly.jwise3-17/+7
Changes are minor -- compiler warning fixes from GCC3, and better log messages.
2003-09-01whitespace fixescjep1-2/+2
2003-08-02Make this compile on NetBSD-1.6.1/shark.kristerw2-7/+15
The package is compiled with -Werror, but the sharks headers are not -Wtraditional safe, so the buld failed. Remove the silly -Wtraditional.
2003-07-29Use /dev/null instead of empty file.jmmv2-6/+3
2003-07-29Convert this package to the bsd.pkg.install.mk framework:jmmv5-37/+53
- Install configuration files under the examples hierarchy. - Use CONF_FILES_PERMS to put the configuration files in place. - Use SUPPORT_FILES_PERMS to put the empty log file in place. - Use RCD_SCRIPTS to handle the rc.d script. While here, add ICBD_OWNER to BUILD_DEFS and use ROOT_USER and ROOT_GROUP where appropiate. As a result, bump PKGREVISION to 1.
2003-07-29Give the -f flag to rm, to avoid a warning message. Fix typo in COMMENT.jmmv1-3/+3
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-02-05We now have a properly versioned distfile for the (alpha) i2cb client, andjwise1-2/+2
we now point users to ${MASTER_SITE_LOCAL} for the distfiles.
2002-11-14Remove old fileshubertf2-14/+0
2002-11-14Import i2cbd-2.0_BETA0: Next generation Internet Citicen's Band chat serverhubertf9-0/+146
I2CB icbd -- the Improved ICB Server ------------------------------------ ICBD is an online chat system which allows a large number of users to participate in realtime online discussions. Among the features of the ICB chat system are: * Simple, fast protocol and efficient polling-based implementation minimize `lag' effects * Persistent user database allows authentication of nicknames, storage of various user information, and leaving messages for users who are not logged on at the moment. * Any user may create groups, and exercise control over those groups, allowing for a wide range of discussion styles. This control includes making groups public or private, visible or invisible, and moderated or unmoderated * The fabulous, famous '/brick' command lends true interactivity to the chat experience :-)