From owner-freebsd-ports@FreeBSD.ORG Tue Aug 7 15:09:30 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B0A616A468 for ; Tue, 7 Aug 2007 15:09:30 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 7A83513C45A for ; Tue, 7 Aug 2007 15:09:30 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 06DE7519CA for ; Tue, 7 Aug 2007 11:09:28 -0400 (EDT) Date: Tue, 7 Aug 2007 16:09:25 +0100 From: RW To: freebsd-ports@freebsd.org Message-ID: <20070807160925.5fa458f0@gumby.homeunix.com.> In-Reply-To: <790a9fff0708070656j77bc1f82l6c267df10e65cdfc@mail.gmail.com> References: <20070807160649.Y22638@obelix.home.rakhesh.com> <790a9fff0708070656j77bc1f82l6c267df10e65cdfc@mail.gmail.com> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Building Pine with PASSFILE option X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2007 15:09:30 -0000 On Tue, 7 Aug 2007 08:56:39 -0500 "Scot Hetzel" wrote: > On 8/7/07, Rakhesh Sasidharan wrote: > > I understand one can compile the email client Pine with an option > > PASSFILE= to enable the option of saving your mail > > account passwords. The Pine website talks about it and so do many > > sites all over the net. I wish something formal could be sorted out for this, for many people the security implications of this are negligible. > > FreeBSD's ports do not seem to offer such an option. I went through > > the Pine Makefile, however, and I see that the "EXTRA_OPTS" > > variable is what's used to compile Pine with extra configurable > > options. > > > > So my question is this: if I want to compile Pine from ports with > > this PASSFILE option, can I do something like the following in > > /usr/ports/mail/pine4? > > > > # make EXTRA_OPTS+=PASSFILE=.pine.pwd install > > > > This won't work from the command line. > > > I used the "+=" coz I got the got the impression that adds onto the > > existing extra options. And if I want to make this permanent, can I > > define it in /etc/make.conf accordingly? > > > > .if ${.CURDIR:M*/mail/pine4} > > EXTRA_OPTS+= PASSFILE=.pine.pwd > > .endif > > > But it will work from /etc/make.conf (using either "=" or "+="), as > long as you don't select LDAP support. Have you actually tried this? A few years ago I couldn't get it, nor several variations on it, to work. IIRC there were a lot of other people who had problems with it on various mailing lists. In the end I created a port patchfile - which gets applied automatically by the ports system. The only problem with it is that if you use portsnap you will have to replace it after a "extract", although an "update" should be OK. Anyway here's the file: $ cat /usr/ports/mail/pine4/files/patch-passfile --- pine/osdep/os-bsf.h.safe Thu Aug 17 20:55:53 2006 +++ pine/osdep/os-bsf.h Thu Aug 17 21:04:04 2006 @@ -54,6 +54,8 @@ ----*/ +#define PASSFILE ".pinepw" + /*---------------------------------------------------------------------- Define this if you want the disk quota to be checked on startup. Of course, this only makes sense if your system has quotas. If it doesn't,