|
Projects |
 
For security, it's recommended you obtain an MD5 checksum from a different mirror.
For other versions of DSPAM, please click here. How is DSPAM versioned? MAJOR.MINOR.PATCH Major releases entail significant changes to the public interfaces or a significant rewrite of code. You won't see new major releases very often, perhaps once every couple of years. Minor releases are made approximately every four-to-six months. Each minor release maintains most if not all of the existing interfaces, but add new features to the software. All odd-versioned minor releases are considered development releases, and all even-versioned minor releases are stable releases. Upgrade steps may be necessary to compensate for minor structural changes. Patch releases are the most common type of release and only involve bug fixes to the existing code. Tentative Release Schedule
CVS Access The DSPAM source tree is available via CVS by using the following commands: cvs -z3 -d :pserver:cvs@cvs.nuclearelephant.com:/usr/local/cvsroot login cvs -z3 -d :pserver:cvs@cvs.nuclearelephant.com:/usr/local/cvsroot checkout dspamThe bleeding-edge version is at the head of the CVS tree, however if you wish to check out a particular release, you may do so by using tags. For example: cvs -z3 -d :pserver:cvs@cvs.nuclearelephant.com:/usr/local/cvsroot checkout -r release_3_6_0 dspam ...will check out the 3.6.0 release of DSPAM. To check out by date, find the date of your desired release from the CHANGELOG and use -D. For example, -D "Apr 11 2004" will check out version 2.0 of DSPAM. In order to build from CVS sources, you will need autoconf, automake, and libtool installed. The versions specifically used in development are listed in configure.ac and Makefile.am. Once you have downloaded the source tree, do the following: cd dspam ./autogen.sh ./configure [options] make && make install |
Hosting provided by Global Net Access
|
Website Content © Sensory Networks, Inc. All Rights Reserved. |
| Reproduction prohibited without permission |
