1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
|
Link: Cone: COnsole Newsreader And Emailer (start)
Link: Cone: COnsole Newsreader And Emailer (parent)
Link: Cone: COnsole Newsreader And Emailer (previous)
Link: Building Cone (next)
Installing Cone
Prev Next
--------------------------------------------------------------------------
Installing Cone
First, make sure that all the necessary requirements (README) are
satisfied. See RPM instructions below if building for Red Hat Linux. See
additional notes below for upgrade instructions. Otherwise:
o Download the Courier Socks 5 proxy client library from
http://www.courier-mta.org/download.php#sox and follow its
installation instructions. Binary RPMs can be built from the source
code tarball by following the procedure outlined in
http://www.courier-mta.org/FAQ.html#rpm using the
"courier-sox-version" tarball, and installing the "courier-sox" and
"courier-sox-devel" binary RPMs afterwards.
This step can be omitted if Socks 5 support is not required. Cone will
compile without the Socks 5 proxy toolkit.
o Download the source code tarball from
http://www.courier-mta.org/download.php#cone and unpack it.
o Set the appropriate environment variables if the compiler or linker
needs any custom command line flags. Run "./configure --help" to list
the available environment variables that specify additional arbitrary
parameters for the C/C++ compiler.
o Run "./configure [options]". See below for a list of available
options.
o Run make.
Note
The GNU version of the command is required. On BSD systems it's the
gmake. Use gmake in this, and the following steps.
o Run make check.
o Run make install.
o Run make install-configure.
Note
Do not forget "make install-configure". It is required.
Unless other options are used, Cone installs in /usr/local:
/usr/local/etc
The configuration file.
/usr/local/bin
The shell script that runs Cone.
/usr/local/libexec
The Cone program itself.
/usr/local/share
Documentation, online help, other files.
/usr/local/lib and /usr/local/include
The development libraries and include files (only if --with-devel
was specified to the configure script).
These installation directories, and other options, may be controlled by
additional options to the configure script:
--prefix, --bindir, and others...
./configure --help lists about a dozen parameters to the
./configure that specify the directories where various files
should be installed.
--with-certdb, --without-certdb, --with-certdb=filename
Install or do not install a default set of trusted SSL certificate
authorities. When using SSL Cone normally checks the server's SSL
certificate, which must be signed by a trusted certificate
authority. Cone's source distribution includes the same list of
trusted certificate authorities as the Mozilla browser. Cone's
certificate list is installed by default, unless Courier is also
installed, in which case Cone's default configuration points to
Courier's rootcerts directory (which contains the same certificate
as Cone's).
--with-certdb installs Cone's trusted SSL certificate authority
list, even if Courier is also installed, in
/usr/local/share/cone/rootcerts (which is derived from the
--datadir default option, as explained by ./configure --help).
--with-certdb=filename installs the trusted SSL certificate
authority list in the directory filename. --without-certdb does
not install Cone's trusted SSL certificate authority list.
--with-gnutls
Select the GnuTLS library even if the OpenSSL library is also
installed. The configure script automatically selects whichever
one is available. The OpenSSL library is selected if both are
present. Use this option to override and select GnuTLS instead.
--with-devel
Install LibMAIL , the mail library used by Cone to access and
handle E-mail messages.
--with-spellcheck=pspell
Cone can use either aspell or pspell for spell checking. aspell is
used if both are installed. This option selects pspell instead.
Upgrading from an earlier version of Cone
Upgrading Cone consists simply of building the new version, and installing
it. The new version will overwrite the previous version. Special upgrade
instructions are given below.
Upgrading from version 0.59 and earlier
The address book format has changed in version 0.60. The old address book
format will be automatically converted to the new format, when necessary,
so no manual intervention is necessary. If Cone is later downgraded to an
earlier version, addresses in an address book that contain non-English
characters will not be shown correctly.
RPM builds
Use the following procedure to build Cone.
The first step is to create a work area for building RPMs. Skip this step
if an RPM build directory is already configured.
echo "%_topdir $HOME/rpm" > $HOME/.rpmmacros
mkdir $HOME/rpm
cd $HOME/rpm
mkdir SOURCES SPECS BUILD SRPMS RPMS
Finally, download the source code to Cone from
http://www.courier-mta.org/download.php#cone. Do not unpack the tarball.
Execute "rpmbuild -ta cone-version.tar.bz2". Two binary RPMs will be
created: the main binary package contains Cone. The "devel" package
contains the LibMAIL library and development files. It is only necessary
to install the main package to run Cone the "devel" subpackage is only
needed for additional development with LibMAIL .
CVS Source checkouts
It is also possible to check out the source from CVS, however additional
requirements apply. Besides the usual prerequisites for building Cone,
additional development software must be installed. See the "Download via
CVS" instructions at http://www.courier-mta.org/status.html. Cone has the
same requirements as Courier for CVS builds (technically, Cone does not
need libtool, but that may change in the future). Make sure that the
prerequisite software is installed, then check out the " Cone" module from
CVS, tagged at revision " Cone-latest". The HEAD may be checked out, but
carries more of the usual risks.
After the module is checked out, run the autobloat shell script to rebuild
the autoconf/automake scripts.
--------------------------------------------------------------------------
Prev Next
Cone: COnsole Newsreader And Emailer Home | ToC Building Cone
References
Visible links
. file:///home/mrsam/src/cone/cone/html/index.html
. file:///home/mrsam/src/cone/cone/html/index.html
. file:///home/mrsam/src/cone/cone/html/index.html
. file:///home/mrsam/src/cone/cone/html/README.html
. file:///home/mrsam/src/cone/cone/html/index.html
. file:///home/mrsam/src/cone/cone/html/README.html
. Building Cone
file:///home/mrsam/src/cone/cone/html/README.html
. http://www.courier-mta.org/download.php#sox
. http://www.courier-mta.org/FAQ.html#rpm
. http://www.courier-mta.org/download.php#cone
. http://www.mozilla.org/
. http://www.courier-mta.org/
. LibMAIL reference
file:///home/mrsam/src/cone/cone/html/libmail.html
. http://www.courier-mta.org/download.php#cone
. http://www.courier-mta.org/status.html
. file:///home/mrsam/src/cone/cone/html/index.html
. file:///home/mrsam/src/cone/cone/html/README.html
. file:///home/mrsam/src/cone/cone/html/index.html
. file:///home/mrsam/src/cone/cone/html/bk01-toc.html
|
