From owner-freebsd-ports Tue Feb 27 7:23: 8 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 852A337B718 for ; Tue, 27 Feb 2001 07:23:02 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 6303 invoked by uid 1000); 27 Feb 2001 15:21:03 -0000 Date: Tue, 27 Feb 2001 17:21:03 +0200 From: Peter Pentchev To: ports@FreeBSD.org Cc: Ville Eerola Subject: RFC: mail/fetchmail Kerberos support patch enhancement Message-ID: <20010227172103.B561@ringworld.oblivion.bg> Mail-Followup-To: ports@FreeBSD.org, Ville Eerola Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Is there anybody out there running fetchmail with Kerberos support? If so, can y'all try the following replacement for files/patch-ad in the port, which would make it *much* easier to apply the FreeBSD-specific patches to each new fetchmail release? This builds with Kerberos 4 support here, however I don't have any kind of Kerberos setup to test it. The attached patch is supposed to replace ALL four chunks of files/patch-ad, not just the first one. If this goes well, I'm thinking of submitting a corresponding configure.in change to the fetchmail developers list - there already *is* FreeBSD-specific configure.in tweaking, let's make it DTRT :) G'luck, Peter -- If there were no counterfactuals, this sentence would not have been paradoxical. --- configure Mon Feb 12 13:16:28 2001 +++ configure Mon Feb 12 13:16:48 2001 @@ -1639,7 +1639,7 @@ if test `uname` = "FreeBSD" then - echo "Adding -lkvm to standard libraries" - LIBS="$LIBS -lkvm" + echo "Adding -lmd -lkvm -lcom_err to standard libraries" + LIBS="$LIBS -lmd -lkvm -lcom_err" fi # Check for Rhapsody special case: it doesn't like -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message