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

57 lines
1.2 KiB
Makefile
Raw Normal View History

Remove quotes surrounding COMMENT*/PERMIT_*/BROKEN
2007-09-15 22:52:56 -04:00
# $OpenBSD: Makefile,v 1.26 2007/09/16 02:53:02 merdely 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
Remove quotes surrounding COMMENT*/PERMIT_*/BROKEN
2007-09-15 22:52:56 -04:00
COMMENT= OpenCM change management system
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
update to opencm 0.1.2alpha8-2
2005-11-30 15:43:44 -05:00
V= 0.1.2alpha8
sV= -2
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
DISTFILES= opencm-${V}${sV}-src.tgz
DISTNAME= opencm-${V}
Let it build with the new boehm-gc, and add a help file to the PLIST.
2007-07-14 18:17:22 -04:00
PKGNAME= opencm-${V}p0
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
CATEGORIES= devel
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
HOMEPAGE= http://www.opencm.org/
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
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
WANTLIB markers
2004-11-23 19:11:03 -05:00
WANTLIB= c crypto ncurses readline ssl z
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
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
MASTER_SITES= ${HOMEPAGE}releases/
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
Let it build with the new boehm-gc, and add a help file to the PLIST.
2007-07-14 18:17:22 -04:00
AUTOCONF_VERSION= 2.57
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
CONFIGURE_STYLE= autoconf
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
LDFLAGS+= -L${LOCALBASE}/lib -lgc
update to 0.1.2alpha5pl2 from 0.1.0alpha18 see http://www.opencm.org/news.html for hilights of this update, major noteworthy changes include: - sxd has gone away, gzfs is 'interim' while 'sxd2' is almost ready - if you have an old sxd repository, read the mailing list archives for how to update (use an interum version) - an incompatible update to the server/client protocol requires that you update both at the same time (as a reminder, this is 'alpha' and as such is subject to incompatible changes like the above. expect more to come when sxd2 emerges) Also, add a 'nogc' flavor that removes the dependency on boehm-gc, at the cost of not free()'ing all memory allocated (read: at the moment, most).
2003-05-23 09:22:14 -04:00
CONFIGURE_ENV= LDFLAGS="${LDFLAGS}" \
update to opencm 0.1.2alpha8-2
2005-11-30 15:43:44 -05:00
CPPFLAGS="${CPPFLAGS} \
Let it build with the new boehm-gc, and add a help file to the PLIST.
2007-07-14 18:17:22 -04:00
-I${LOCALBASE}/include -I${LOCALBASE}/include/gc \
-DUSE_SYSTEM_ZLIB" \
update to 0.1.2alpha5pl2 from 0.1.0alpha18 see http://www.opencm.org/news.html for hilights of this update, major noteworthy changes include: - sxd has gone away, gzfs is 'interim' while 'sxd2' is almost ready - if you have an old sxd repository, read the mailing list archives for how to update (use an interum version) - an incompatible update to the server/client protocol requires that you update both at the same time (as a reminder, this is 'alpha' and as such is subject to incompatible changes like the above. expect more to come when sxd2 emerges) Also, add a 'nogc' flavor that removes the dependency on boehm-gc, at the cost of not free()'ing all memory allocated (read: at the moment, most).
2003-05-23 09:22:14 -04:00
vl_cv_lib_kerberos=1
MAKE_ENV= LDFLAGS="${LDFLAGS}"
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
oops, as pointed out a long time ago, regress is broken. Until today, I did not realize how badly. The entire tests/ subdir is missing from the release, but is available if you wish to checkout their repository. hmm...
2003-06-12 17:33:36 -04:00
NO_REGRESS= Yes
update to 0.1.2alpha5pl2 from 0.1.0alpha18 see http://www.opencm.org/news.html for hilights of this update, major noteworthy changes include: - sxd has gone away, gzfs is 'interim' while 'sxd2' is almost ready - if you have an old sxd repository, read the mailing list archives for how to update (use an interum version) - an incompatible update to the server/client protocol requires that you update both at the same time (as a reminder, this is 'alpha' and as such is subject to incompatible changes like the above. expect more to come when sxd2 emerges) Also, add a 'nogc' flavor that removes the dependency on boehm-gc, at the cost of not free()'ing all memory allocated (read: at the moment, most).
2003-05-23 09:22:14 -04:00
MAKE_FLAGS+= TEXI2DVI=: DVIPS=:
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
MAKE_FLAGS+= LIBZ=-lz USOURCE_SUBDIRS="libgdiff src"
MAKE_FLAGS+= LIBGC=
gnu-make magic will fuck up directory names if some shit is already on the disk. avoid that.
2005-08-09 05:07:24 -04:00
MAKE_FLAGS+= infodir=${PREFIX}/info
MAKE_FLAGS+= mandir=${PREFIX}/man
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
FAKE_FLAGS= ${MAKE_FLAGS}
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
post-install:
switch to new plist, killing a few install scripts along the way.
2004-09-14 19:43:54 -04:00
gunzip ${PREFIX}/info/opencm.info.gz
update to 0.1.2alpha5pl2 from 0.1.0alpha18 see http://www.opencm.org/news.html for hilights of this update, major noteworthy changes include: - sxd has gone away, gzfs is 'interim' while 'sxd2' is almost ready - if you have an old sxd repository, read the mailing list archives for how to update (use an interum version) - an incompatible update to the server/client protocol requires that you update both at the same time (as a reminder, this is 'alpha' and as such is subject to incompatible changes like the above. expect more to come when sxd2 emerges) Also, add a 'nogc' flavor that removes the dependency on boehm-gc, at the cost of not free()'ing all memory allocated (read: at the moment, most).
2003-05-23 09:22:14 -04:00
new libspecs
2006-08-01 19:39:08 -04:00
LIB_DEPENDS= gc.>=1:boehm-gc->=6.2: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
WRKSRC= ${WRKDIST}/base
.include <bsd.port.mk>
Reference in New Issue Copy Permalink