| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2003-01-28 | Instead of including bsd.pkg.install.mk directly in a package Makefile, | jlam | 1 | -2/+3 | |
| have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set to "YES". This enforces the requirement that bsd.pkg.install.mk be included at the end of a package Makefile. Idea suggested by Julio M. Merino Vidal <jmmv at menta.net>. | |||||
| 2002-09-20 | Make these scripts more portable by taking advantage of automatic rc.d | grant | 1 | -2/+2 | |
| script handling and using @RCD_SCRIPTS_SHELL@. as discussed with jlam. | |||||
| 2002-09-19 | Take advantage of the auto-generation and installation of rc.d scripts. | jlam | 1 | -3/+1 | |
| 2002-09-01 | Move default definitions of P4USER, P4GROUP, P4ROOT, and P4PORT to | schmonz | 1 | -5/+1 | |
| bsd.pkg.defaults.mk. | |||||
| 2002-09-01 | Initial import of Perforce SCM server, release 2002.1. | schmonz | 5 | -0/+177 | |
| 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. | |||||
 |
index : pkgsrc | |
| [no description] | Dyson |
| summaryrefslogtreecommitdiff |