head	1.2;
access;
symbols
	RELEASE_8_3_0:1.1
	RELEASE_9_0_0:1.1
	RELEASE_7_4_0:1.1
	RELEASE_8_2_0:1.1
	RELEASE_6_EOL:1.1
	RELEASE_8_1_0:1.1
	RELEASE_7_3_0:1.1
	RELEASE_8_0_0:1.1
	RELEASE_7_2_0:1.1
	RELEASE_7_1_0:1.1
	RELEASE_6_4_0:1.1
	RELEASE_5_EOL:1.1
	RELEASE_7_0_0:1.1
	RELEASE_6_3_0:1.1
	PRE_XORG_7:1.1
	RELEASE_4_EOL:1.1
	RELEASE_6_2_0:1.1
	RELEASE_6_1_0:1.1
	RELEASE_5_5_0:1.1;
locks; strict;
comment	@# @;


1.2
date	2012.11.17.06.01.19;	author svnexp;	state Exp;
branches;
next	1.1;

1.1
date	2006.01.07.07.57.51;	author edwin;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Switch exporter over
@
text
@# New ports collection makefile for:	samhain-server
# Date created:				2005-10-31
# Whom:					David Thiel
#
# $FreeBSD: head/security/samhain-server/Makefile 300897 2012-07-14 14:29:18Z beat $
#

# This port recognizes the following non-boolean tunables:
#
# WITH_RUNAS_USER:
#       Whe building with "WITH_SERVER" defined, the username of the
#       account Yule will run as. Defaults to "yule". If using
#       WITH_GPG, ensure that this user exists and has a pgp
#       keypair before installing.


PKGNAMESUFFIX=	-server

COMMENT=	Log server for the Samhain IDS

WITH_SERVER=	yes

MASTERDIR=	${.CURDIR}/../../security/samhain

.include "${MASTERDIR}/Makefile"
@


1.1
log
@Update: security/samhain 2.0.10 -> 2.1.0

        Updating the Samhain integrity checking system to 2.1.0, a
        bugfix release.

        It's been requested by several people to break Samhain out
        into separate client and server ports. This PR does that,
        with a samhain-client and samhain-server port, as slave
        ports off of samhain. I'm not sure the best way to submit
        a PR to do this kind of action, but here is a shar of all
        three ports. If another format is desired, please let me
        know.  I'm also interested in feedback on the approach used
        for splitting these out.

PR:             ports/90305
Submitted by:   David Thiel <lx@@redundancy.redundancy.org>
@
text
@d5 1
a5 1
# $FreeBSD$
@

