I just downloaded the mac version and installed it.
On Jun 8, 2006, at 1:19 PM, Travis Siegel wrote:
I'll reply here, because others may find it useful.
We have several computers on our local network. Since the names are
all of the .local variety, we can easily send mail back and forth
between machines, if we need to exchange files, notes, or just want
to say hi. I use pine for this kind of mail, it's all stored on my
mini (which acts as the server for the whole network) and everyone
else can also login via ssh and use pine, or they can use a pop3
client (like mail) to download the messages off the server if so
desired. I don't, just because I like having the local messages in a
different place. I could, but simply choose not to.
Now, as far as installing pine, this takes a bit of command-line
work. If you've never compiled programs before, then you won't want
to do it my way, you'll want instead to install fink or darwin ports,
and get pine that way. However, if you're comfortable with
compilers, have them installed, and know your way around a terminal
shell, here's what you do to get pine on your system.
First, go to the university of washington where pine is maintained.
ftp.cac.washington.edu.
Log in either via safari or terminal. i find terminal works better
for ftp sessions than does safari, as it usually hands them off to
finder which is real cool, since they become a drive on your system,
but generally is way to slow for my tastes.
Change to the pine directory.
Download the latest tarball file (pine-4.64.tar.gz) is the latest as
of this writing.
Find it in the finder, and click on it to expand it (then click the
tar file to expand that one too) or, in terminal you can type
tar -zxfpine-4.64.tar.gz and it'll do it in one step.
Change into the pine-4.64 directory, and type ./configure
then just type make all (or just make if you don't care about
everything being installed) and away it will go.
After that, you can either use pine where it is, or move it to your /
usr/local/bin directory, and add that to your path (using the .bashrc
file) and you're all set.
Or, if you become root, you can then type make install and pine will
be installed for you. Location is also /usr/local/bin if I'm not
mistaken, unless it gets changed during configuration or manually via
command-line parameters.
When this is all done, you'll have a perfectly usable copy of pine on
your system, and can begin running, configuring, and using immediately.
Like I said, there's a bit of difference from the way it works in
terminal as opposed to linux, but I find that if you want automatic
speech, it can be more or less done (at the expense of extra output)
if you leave the highlight bar turned on. I usually turn this off,
and just hunt for the greater than symbol to see what line I'm on,
but this mode works well enough on OSX in terminal that I leave it
on, although it does slow things down quite a bit.
Of course, once you select a message, it works just like pine always
does.
If none of this makes any sense, then pine probably isn't the mailer
of choice for your purposes, or you really should think about fink or
darwin ports, as the bulk of the work gets done for you in that case.
Hope this helps someone.
