From owner-freebsd-ports  Mon Sep 18 12:13:10 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0F68137B423; Mon, 18 Sep 2000 12:13:08 -0700 (PDT)
Received: (from ade@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id MAA16392;
	Mon, 18 Sep 2000 12:13:08 -0700 (PDT)
	(envelope-from ade@FreeBSD.org)
Date: Mon, 18 Sep 2000 12:13:08 -0700 (PDT)
From: <ade@FreeBSD.org>
Message-Id: <200009181913.MAA16392@freefall.freebsd.org>
To: doconnor@cain.gsoft.com.au, ade@FreeBSD.org,
	freebsd-ports@FreeBSD.org
Subject: Re: ports/10634: Update the hylafax port to do a client install
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Update the hylafax port to do a client install

State-Changed-From-To: analyzed->closed
State-Changed-By: ade
State-Changed-When: Mon Sep 18 11:54:49 PDT 2000
State-Changed-Why: 
Timeout (long time) in analyzed.  Whilst the audit trail mentions
that someone was going to be updating the client-only bits and
pieces from this PR, the port has changed so much since its
BROKEN days, that there's just no way this is ever going to
apply cleanly.

If an enterprising soul really wants client-only support in
hylafax, submit diffs against the current port in a new PR
and we'll go from there.  You will be required to take maintainership
as part of this process.  Just kidding.  Maybe :)

http://www.freebsd.org/cgi/query-pr.cgi?pr=10634


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message