Re: Re: [Fwd: Which version is suitable for FC6 System]

Ryan Barrett <[email protected]>
Newsgroups gmane.mail.pine.general
Message-ID <[email protected]>
On Mon, 22 Jan 2007, Rex Dieter wrote:

>> you might also look at alpine, the "next generation" of pine.
>> http://www.washington.edu/alpine/
>
> Doesn't appear to be available to the general public, yet. ):

it hasn't been advertised widely, but it's been announced on the alpine 
mailing list:

https://mailman1.u.washington.edu/mailman/listinfo/alpine-alpha

you can download it here:

ftp://ftp.cac.washington.edu/alpine/

there's been a lot of activity on that list, mostly people reporting issues 
they've found in the alpha test. here's the original announcement email:


  ---------- Forwarded message ----------
  Date: Wed, 29 Nov 2006 17:30:58 -0800 (PST)
  From: Jeff Franklin <[email protected]>
  Reply-To: [email protected]
  To: Alpine Pre-Release Team <[email protected]>
  Subject: [Alpine-alpha] Announcing Alpine 0.8

At long last!  We're pleased to announce the first pre-release of the Alpine 
Messaging System.  Today's pre-release includes all source necessary to 
build Unix, Windows and Web-based mail user agents and accompanying 
utilites.

On the surface, Alpine and friends will appear strikingly similar to their 
cousins from the Pine Mail System, but underneath little remains the same. 
First, you'll find the source completely restructured.  New source 
directories have appeared and source files are smaller and divided by 
function.

Next, you'll find a completely updated build process based on GNU autotools. 
No port abbreviations.  No custom build script.  Just run "./configure" and
"make" and you're off.

Unfortunately, two exceptions remain.  The c-client library build is based 
on static makefiles and specific os-based targets.  The good news is the 
configure script should generate appropriate targets and build the library 
with minimum intervention.  The Windows build, which also uses static make 
files, does not use configure and currently requires more to be done by hand 
than we would like.

We'd also like to stress that the source released today has NOT been 
thoroughly tested.  Not feature-wise.  Not system diversity-wise.  Not much 
at all. Beyond daily use of current builds, we have not attempted any amount 
of formal testing nor have we tried building on any platforms beyond those 
we use for development - Red Hat Enterprise and Fedore Core Linux, Apple OS 
X, and Windows XP.

What's more, we're not finished.  While you familiarize yourself with the 
new source, build process and features, we will continue to put the 
finishing touches on the final release as well as address the comments and 
questions that you raise.

And speaking of comments and questions, the only thing less complete than 
the testing is the documentation.  The built-in help should be reasonably 
accurate, but pretty much everything within the doc/ directory has yet to 
receive any attention.  This includes the technical notes.

That said, the first pre-release version of Alpine can be found at:

              ftp://ftp.cac.washington.edu/alpine/alpine-0.8.tar.gz
              (MD5: 5a5d46189b3cc82b84b146b87c9bef2a)

For those wishing to run Alpine for Windows, we've already built a zip-file 
package, which can be found at:

              ftp://ftp.cac.washington.edu/alpine/alpine-0.8-wnt.zip
              (MD5: 31d644ada7ac7182ca048181cb3fd57d)

Lastly, our team's goal is to produce as fully featured and stable a mail 
system as possible.  We also realize that we cannot possibly achieve that 
goal alone, so it is in this team spirit that we offer these pre-release 
sources. Please share your comments and questions with us.

Thanks and enjoy!

The Alpine Messaging System Team

-Ryan

--
http://snarfed.org/
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.