From owner-freebsd-ports Sun Aug 13 00:14:44 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA13579 for ports-outgoing; Sun, 13 Aug 1995 00:14:44 -0700 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA13567 for ; Sun, 13 Aug 1995 00:14:32 -0700 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.11/8.6.9) with ESMTP id JAA14182; Sun, 13 Aug 1995 09:14:25 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.11/8.6.9) with SMTP id JAA18649; Sun, 13 Aug 1995 09:14:23 +0200 Message-Id: <199508130714.JAA18649@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: "Jordan K. Hubbard" cc: ports@freefall.FreeBSD.org Subject: Re: pop support in MH on by default? Date: Sun, 13 Aug 1995 09:14:22 +0200 From: Mark Murray Sender: ports-owner@FreeBSD.org Precedence: bulk > In /usr/ports/mail/mh/patches/patch-aa we add a default FreeBSD > config file that has POP support turned off by default. This means > that a potential pop user has to run the build in two stages, modifying > conf/FreeBSD in between. This somewhat dependant on said user knowing > quite a bit about the ports collection and isn't exactly what one would > call a general mechanism. I see two possibilities: > > 1. Enable pop by default and assume that the -lcrypt will, at the worst, go > to the MD5 encryption (libscrypt) version. > > 2. Put something into the config section that asks interactively if the user > wants POP support and tweaks the file accordingly. I'd go with #2, myself. What does your pop-compliant config file look like? I'll bung it in... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key