Subject: RE: PASSFILE

From: Hong Tian <[email-masked]>
Date: Mon, 7 Oct 2002 20:19:13 -0400

Eduardo and Richard,

It works!

One more question: What is the different between "pine4.44/pine/pine.h" and
"pine/osdep/os-lnx.h"? Could I use either one of them?

Thanks!
Hong

-----Original Message-----
From: Eduardo Chappa [mailto:[email-masked]]
Sent: Monday, October 07, 2002 7:41 PM
To: Hong Tian
Cc: Pine Discussion Forum
Subject: Re: PASSFILE

*** Hong Tian ([email-masked]) wrote in the pine-info list today:

:) (1) A pine user here requests not to type password when starting Pine
:) after he logins his user account on RedHat 7.3 Linux. I have to compile
:) the pine with PASSFILE Compile-time option to resolve it. The problem
:) is that I am not clear how to compile pine with PASSFILE. I tried
:) several ways, but it still didn't work. Anyone knows how to do it?

Edit the file "pine4.44/pine/pine.h" and add a line like

#define PASSFILE	"lrh"

to that file. This will use a file called "lrh", located in the home
directory of the user using Pine to store passwords. Notice that you can
give a relative path to $HOME too, and it could be a hidden file. Once you
have rebuilt Pine, simply create an empty file with that name on the
location that you specified. The rest of the process is taken care by Pine
once you start it again.

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/

---

From: Eduardo Chappa <[email-masked]>
Date: Mon, 7 Oct 2002 20:01:35 -0700 (PDT)

*** Hong Tian ([email-masked]) wrote today:

:) Eduardo and Richard,
:)
:) It works!
:)
:) One more question: What is the different between "pine4.44/pine/pine.h"
:) and "pine/osdep/os-lnx.h"? Could I use either one of them?

Normally files os-xxx.h are reserved for system specific settings. The
file pine.h is for definition of pine variables. Any file ".h" that you
use is fine, see the file headers.h to see why. The reason why I never
recommend os-xxx.h, is because I don't know what the value of xxx in
general is, so I go for what's safe, which is the file pine.h (or several
others).

---

From: Nancy McGough <[email-masked]>
Date: Tue, 08 Oct 2002 14:34:40 +0100

--On Monday, 07 October2002 20:01 -0700 Eduardo Chappa
<[email-masked]> wrote:

> The reason why I never recommend os-xxx.h, is because I
> don't know what the value of xxx in general is, so I go for
> what's safe, which is the file pine.h (or several others).

Is it possible to specify PASSFILE as a command-line argument to
the build command? If so, I think this would be the easiest way to
do this because:

1) It does not involve finding and editing (and potentially
corrupting) one of the build files

and 

2) It could be put into a script and used for future builds. It
seems like I'm always downloading & building Pine and it would be
nice to just use my "mypinebuild" script to do all the configuring
that I want.

Thanks,
Nancy