Date: Tue, 3 Dec 2002 13:23:52 +0100 (CET) From: Roman Neuhauser <neuhauser@bellavista.cz> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/45963: the port looks for majordomo.cf in /etc Message-ID: <20021203122352.565322FDAEE@freepuppy.bellavista.cz>
next in thread | raw e-mail | index | archive | help
>Number: 45963
>Category: ports
>Synopsis: the port looks for majordomo.cf in /etc
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Dec 03 04:30:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Roman Neuhauser
>Release: FreeBSD 4.7-STABLE i386
>Organization:
>Environment:
System: FreeBSD freepuppy.bellavista.cz 4.7-STABLE FreeBSD 4.7-STABLE #0: Fri Oct 11 16:16:01 CEST 2002 roman@freepuppy.bellavista.cz:/usr/obj/usr/src/sys/FREEPUPPY2_3 i386
>Description:
majordomo installed from the port doesn't work out of the box: one either
has to move ${PREFIX}/majordomo/majordomo.cf to /etc/majordomo.cf, or set
the MAJORDOMO_CF envvar. This patch should fix this problem.
I have a feeling this is a hack, and should be addressed in a different way,
but couldn't remember another port solving this problem off-hand. If there
is a better way to do this let me know, and I'll rework the patch.
Also, since the send-pr man page doesn't clearly state whether the -a option
can be repeated, I'm attaching a shar.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021203122352.565322FDAEE>