cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0e41eafb18
openbsd-ports/devel/opencm/Makefile

66 lines
1.6 KiB
Makefile
Raw Normal View History

remove version number from tetex dependency, I missed this one when updating tetex reported by wilfried@ ok pvalchev@
2003-03-04 16:41:00 -05:00
# $OpenBSD: Makefile,v 1.10 2003/03/04 21:41:00 sturm Exp $
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
COMMENT= "OpenCM change management system"
COMMENT-docs= "OpenCM Documentation"
opencm-alpha18pl2 .. another upwards-only compatible update
2002-10-23 16:57:30 -04:00
V= 0.1.0alpha18pl2
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
sV= -1
DISTNAME= opencm-${V}${sV}-src
PKGNAME= opencm-${V}
update to alpha18pl1 WARNING: Anyone using OpenCM must realize that with this update, you will no longer be able to talk to older repositories. The repository itself upgrades fine, just the wire protocol changed incompatibly. Recap: alpha18pl1 and beyond will not talk to alpha17 and below, and vica versa.
2002-10-23 11:35:54 -04:00
FULLPKGNAME= opencm-${V}
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
FULLPKGNAME-docs= opencm-docs-${V}
CATEGORIES= devel
HOMEPAGE= http://www.opencm.org
MAINTAINER= Todd T. Fries <todd@openbsd.org>
# BSD/(GPL for diff3)
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
# where the source files and patches can be fetched
#
MASTER_SITES= http://www.opencm.org/releases/
EXTRACT_SUFX= .tgz
BUILD_DEPENDS= gc.1:boehm-gc->=6.0:devel/boehm-gc
from wilfried@ .. properly use LIB_DEPENDS and use the PLIST${SUBPACKAGE} so we don't end up with two packages with docs with the docs flavor. Thanks!
2002-08-28 10:38:25 -04:00
LIB_DEPENDS= gc.1::devel/boehm-gc
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
USE_GMAKE= Yes
MODGNU_CONFIG_GUESS_DIRS= ${WRKSRC}
CONFIGURE_STYLE= autoconf
CONFIGURE_ARGS+= ${CONFIGURE_SHARED}
update to alpha17 (finally some activity!)
2002-10-11 08:27:00 -04:00
CONFIGURE_ENV= LDFLAGS="-L${LOCALBASE}/lib -lz -lgc" \
respect CPPFLAGS
2002-09-12 11:26:33 -04:00
CPPFLAGS="${CPPFLAGS} -I${LOCALBASE}/include"
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
FLAVORS=docs
FLAVOR?=
MULTI_PACKAGES=
.if ${FLAVOR:L:Mdocs}
remove version number from tetex dependency, I missed this one when updating tetex reported by wilfried@ ok pvalchev@
2003-03-04 16:41:00 -05:00
BUILD_DEPENDS+= :teTeX_base-*:print/teTeX/base
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
MULTI_PACKAGES+= -docs
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/opencm
${INSTALL_DATA} ${WRKSRC}/doc/opencm.html ${PREFIX}/share/doc/opencm
${INSTALL_DATA} ${WRKSRC}/doc/opencm.ps ${PREFIX}/share/doc/opencm
.else
update to alpha17 (finally some activity!)
2002-10-11 08:27:00 -04:00
MAKE_FLAGS+= TEXI2DVI=: DVIPS=:
FAKE_FLAGS+= TEXI2DVI=: DVIPS=:
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
.endif
update to alpha17 (finally some activity!)
2002-10-11 08:27:00 -04:00
MAKE_FLAGS+= LIBZ= LIBGC= USOURCE_SUBDIRS="libgdiff src"
FAKE_FLAGS+= LIBZ= LIBGC= USOURCE_SUBDIRS="libgdiff src"
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
from wilfried@ .. properly use LIB_DEPENDS and use the PLIST${SUBPACKAGE} so we don't end up with two packages with docs with the docs flavor. Thanks!
2002-08-28 10:38:25 -04:00
PLIST= ${PKGDIR}/PLIST${SUBPACKAGE}
OpenCM alpha16 OpenCM is designed as a secure, high-integrity replacement for CVS. A list of the key features can be found on the features page. While not as ``feature rich'' as CVS, it supports some useful things that CVS lacks. Briefly, OpenCM provides first-class support for renames and configuration, cryptographic authentication and access control, and first-class branches. The OpenCM project was originally started because we needed a secure, high-integrity configuration management system for the EROS project. Alternatives, such as BitKeeper, Subversion, and PerForce, either did not meet our requirements or were not available at the time the work started. We had previously used CVS, but it's absence of real branches and configurations finally drove us to build a better tool.
2002-08-27 12:46:09 -04:00
WRKDIST= ${WRKDIR}/${PKGNAME}
WRKSRC= ${WRKDIST}/base
.include <bsd.port.mk>
Reference in New Issue Copy Permalink