[Midnightbsd-cvs] mports: mports/devel: Add cvsps and cvsps-devel.

[laffer1 at midnightbsd.org]

Log Message:
-----------
Add cvsps and cvsps-devel.

Modified Files:
--------------
    mports/devel:
        Makefile (r1.184 -> r1.185)

Added Files:
-----------
    mports/devel/cvsps:
        Makefile (r1.1)
        distinfo (r1.1)
        pkg-descr (r1.1)
    mports/devel/cvsps/files:
        patch-cvsps.c (r1.1)
    mports/devel/cvsps-devel:
        Makefile (r1.1)
        distinfo (r1.1)
        pkg-descr (r1.1)
    mports/devel/cvsps-devel/files:
        patch-cvsps.c (r1.1)

-------------- next part --------------
--- /dev/null
+++ devel/cvsps/pkg-descr
@@ -0,0 +1,9 @@
+CVSps is a program for generating 'patchset' information from a CVS
+repository. A patchset in this case is defined as a set of changes made
+to a collection of files, and all committed at the same time (using a
+single 'cvs commit' command). This information is valuable to seeing the
+big picture of the evolution of a cvs project. While cvs tracks revision
+information, it is often difficult to see what changes were committed
+'atomically' to the repository.
+
+WWW: http://www.cobite.com/cvsps/
--- /dev/null
+++ devel/cvsps/Makefile
@@ -0,0 +1,38 @@
+# ex:ts=8
+# Ports collection makefile for:	cvsps
+# Date Created:			Jan 4, 2008
+# Whom:				laffer1
+#
+# $MidnightBSD: mports/devel/cvsps/Makefile,v 1.1 2008/01/04 15:21:03 laffer1 Exp $
+#
+
+PORTNAME=	cvsps
+PORTVERSION=	2.1
+PORTREVISION=	0
+CATEGORIES=	devel
+MASTER_SITES=	http://www.cobite.com/cvsps/
+
+MAINTAINER=	ports at MidnightBSD.org
+COMMENT=	Create patchset information from CVS
+LICENSE=	gpl2
+
+USE_GMAKE=	yes
+ALL_TARGET=	cvsps
+
+MAN1=		cvsps.1
+PLIST_FILES=	bin/cvsps
+
+.if !defined(NOPORTDOCS)
+PORTDOCS=	README
+.endif
+
+do-install:
+	${INSTALL_PROGRAM} ${WRKSRC}/cvsps ${PREFIX}/bin
+	${INSTALL_MAN} ${WRKSRC}/cvsps.1 ${MANPREFIX}/man/man1
+
+.if !defined(NOPORTDOCS)
+	${MKDIR} ${DOCSDIR}
+	${INSTALL_DATA} ${WRKSRC}/README ${DOCSDIR}
+.endif
+
+.include <bsd.port.mk>
--- /dev/null
+++ devel/cvsps/distinfo
@@ -0,0 +1,3 @@
+MD5 (cvsps-2.1.tar.gz) = bde2110ed9f5d14de8f8cb04e9d596fe
+SHA256 (cvsps-2.1.tar.gz) = 91d3198b33463861a581686d5fcf99a5c484e7c4d819384c04fda9cafec1075a
+SIZE (cvsps-2.1.tar.gz) = 61634
--- /dev/null
+++ devel/cvsps/files/patch-cvsps.c
@@ -0,0 +1,12 @@
+--- cvsps.c.orig	Wed Aug  9 21:59:54 2006
++++ cvsps.c	Wed Aug  9 22:00:17 2006
+@@ -2551,8 +2551,8 @@
+     for (next = ps->members.next; next != &ps->members; next = next->next) 
+     {
+ 	PatchSetMember * psm = list_entry(next, PatchSetMember, link);
+-	rev = psm->pre_rev;
+ 	int d1, d2;
++	rev = psm->pre_rev;
+ 
+ 	/* the reason this is at all complicated has to do with a 
+ 	 * branch off of a branch.  it is possible (and indeed 
--- /dev/null
+++ devel/cvsps-devel/pkg-descr
@@ -0,0 +1,9 @@
+CVSps is a program for generating 'patchset' information from a CVS
+repository. A patchset in this case is defined as a set of changes made
+to a collection of files, and all committed at the same time (using a
+single 'cvs commit' command). This information is valuable to seeing the
+big picture of the evolution of a cvs project. While cvs tracks revision
+information, it is often difficult to see what changes were committed
+'atomically' to the repository.
+
+WWW: http://www.cobite.com/cvsps/
--- /dev/null
+++ devel/cvsps-devel/Makefile
@@ -0,0 +1,30 @@
+# ex:ts=8
+# Ports collection makefile for:	cvsps
+# Date Created:			Jan 4, 2008
+# Whom:				laffer1
+#
+# $MidnightBSD: mports/devel/cvsps-devel/Makefile,v 1.1 2008/01/04 15:21:03 laffer1 Exp $
+#
+
+PORTNAME=	cvsps
+DISTVERSION=	2.1
+CATEGORIES=	devel
+MASTER_SITES=	http://www.cobite.com/cvsps/
+PKGNAMESUFFIX?=	-devel
+
+MAINTAINER=	ports at MidnightBSD.org
+COMMENT=	CVS patchsets
+LICENSE=	gpl2
+
+CONFLICTS=	cvsps-1.*
+
+USE_GMAKE=	yes
+
+MAN1=		cvsps.1
+PLIST_FILES=	bin/cvsps
+
+do-install:
+	${INSTALL_PROGRAM} ${WRKSRC}/cvsps ${PREFIX}/bin
+	${INSTALL_MAN} ${WRKSRC}/cvsps.1 ${MANPREFIX}/man/man1
+
+.include <bsd.port.mk>
--- /dev/null
+++ devel/cvsps-devel/distinfo
@@ -0,0 +1,3 @@
+MD5 (cvsps-2.1.tar.gz) = bde2110ed9f5d14de8f8cb04e9d596fe
+SHA256 (cvsps-2.1.tar.gz) = 91d3198b33463861a581686d5fcf99a5c484e7c4d819384c04fda9cafec1075a
+SIZE (cvsps-2.1.tar.gz) = 61634
Index: Makefile
===================================================================
RCS file: /home/cvs/mports/devel/Makefile,v
retrieving revision 1.184
retrieving revision 1.185
diff -L devel/Makefile -L devel/Makefile -u -r1.184 -r1.185
--- devel/Makefile
+++ devel/Makefile
@@ -30,6 +30,8 @@
     SUBDIR += cscope
     SUBDIR += cvsgraph
     SUBDIR += cvsnt
+    SUBDIR += cvsps
+    SUBDIR += cvsps-devel
     SUBDIR += cvsweb
     SUBDIR += cvsweb3
     SUBDIR += dbus
--- /dev/null
+++ devel/cvsps-devel/files/patch-cvsps.c
@@ -0,0 +1,13 @@
+--- cvsps.c.orig	Sun Jul 31 13:23:28 2005
++++ cvsps.c	Sun Jul 31 13:23:36 2005
+@@ -2550,9 +2550,9 @@
+ 
+     for (next = ps->members.next; next != &ps->members; next = next->next) 
+     {
++	int d1, d2;
+ 	PatchSetMember * psm = list_entry(next, PatchSetMember, link);
+ 	rev = psm->pre_rev;
+-	int d1, d2;
+ 
+ 	/* the reason this is at all complicated has to do with a 
+ 	 * branch off of a branch.  it is possible (and indeed