summaryrefslogtreecommitdiff
path: root/shells/mudsh
AgeCommit message (Collapse)AuthorFilesLines
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-01-21Update package Makefile now that bsd.pkg.extract.mk is using thejlam1-2/+1
"extract" script for extraction. Many cases where a custom EXTRACT_CMD simply copied the distfile into the work directory are no longer needed. The extract script also hides differences between pax and tar behind a common command-line interface, so we no longer need code that's conditional on whether EXTRACT_USING is tar or pax.
2005-07-16Remove some unnecessarily strong dependencies on perl that resultedjlam1-2/+2
from including perl5/buildlink3.mk. These packages just need the Perl interpreter, and can just add "perl" to USE_TOOLS instead.
2005-06-17Create directories before installing files into them.jlam1-1/+3
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digests.agc1-1/+2
2004-04-18Convert to buildlink3.snj1-3/+3
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-3/+3
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2003-05-06Drop trailing whitespace. Ok'ed by wiz.jmmv1-2/+2
2003-03-29Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.jmmv1-2/+2
2002-11-18Initial import of the MUD-Shell into the NetBSD packages collection ascjep4-0/+40
shells/mudsh. Is there any reason why a shell (or command line) cannot be as tolerant or as intelligent as a text adventure game like Zork, or a MUD (Multi User Dungeon)? Is there any reason why a shell cannot work like such a game? ("Go North", etc.) Actually, the answer is no and this is a perl implementation to prove it. Have fun, and don't get eaten by a Grue!