summaryrefslogtreecommitdiff
path: root/devel/p4
AgeCommit message (Collapse)AuthorFilesLines
2006-06-17Fixed some pkglint warnings.rillig2-27/+27
2005-10-20Add RMD160 checksums.wiz1-1/+10
2005-06-16Create directories before installing files into them.jlam1-1/+3
2005-05-22Removed NO_PATCH and replaced #defined with "yes" to make pkglint happy.rillig1-4/+3
2005-02-23Add RMD160 digests.agc1-1/+2
2004-01-22whitespace fixesgrant1-23/+23
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-2/+2
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-03-29Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.jmmv1-2/+2
2002-09-05For NetBSD/powerpc, choose the LinuxPPC binary.schmonz1-2/+4
2002-09-01Add P4ARCH quirk for p4web on NetBSD/i386.schmonz1-1/+5
2002-09-01Revert import botch.schmonz5-166/+33
2002-09-01Initial import of Perforce SCM server, release 2002.1.schmonz5-33/+166
P4D, the Perforce Server, manages the Perforce central file repository (the "depot"), tracks Perforce user operations, and records activity in the Perforce SCM database. You need one Perforce Server to support all of the users in your enterprise.
2002-09-01Initial import of Perforce SCM client, release 2002.1.schmonz5-0/+105
P4 is a small, self-contained Perforce client program that offers access to all Perforce SCM (software configuration management) features through a command line. It can be used in command shells and scripts, and is the ideal interface for automated processes that perform SCM tasks.