Opened 18 years ago

Closed 18 years ago

#2177 closed enhancement (fixed)

Exim version entities for easier updates

Reported by: Arnold the Frog Owned by: Randy McMurchy
Priority: normal Milestone: 6.2.0
Component: BOOK Version: SVN
Severity: normal Keywords: exim
Cc:

Description

Exim

All corrections are with reference to http://www.linuxfromscratch.org/blfs/view/svn/server/mail.html#exim
marked as "Last updated on 2006-06-21 11:26:07 -0500"

Correction to version numbers

All three references to exim-4.43-2 should be to the current version number
instead (4.61 in Book, though the very latest version is 4.63).

Update to on-line documentation

The references to the on-line documentation are given to http://www.exim.org/exim-html-4.40/doc/html/
The documentation for exim-4.62 is now on line at
http://www.exim.org/exim-html-4.62/doc/html/

Pre-built Documentation

Tarballs of pre-built documentation for exim are available in
various formats from the master site http://www.exim.org/ftp/exim4/
and its many mirrors.
Each of the 4.6.* releases so far (0, 1, 2, 3) has a set.
They are called exim-{html,pdf,postscript,texinfo}-<version>.tar.bz2 ,
and are available for 4.6{0,1,2,3} releases, among others.

By the way, the "University of Cambridge" here means Dr. Phil Hazel of the
Computer Laboratory, who is a Good Thing.

Change History (3)

comment:1 by dnicholson@…, 18 years ago

Since all these versions come in and out of sync all the time, I propose adding a couple more entities to simplify editing. I think this would help:

<!ENTITY exim-online-doc-version "4.62">

Alternatively, we could download the pre-built documentation, install it on disk and point the ulinks to where they should be installed. I'm already planning on adding an Additional Download link to the documentation.

comment:2 by Randy McMurchy, 18 years ago

Owner: changed from blfs-book@… to Randy McMurchy
Status: newassigned
Summary: exim version references need un-confusingExim version entities for easier updates
Type: defectenhancement

The version entity for the docs sounds like a great idea. I'm not sure about the "adding an Additional Download link to the documentation". I can't figure out what that means.

Since there is complete text-based docs shipped in the package tarball, there really isn't a need for BLFS to provide instructions for installing alternate forms of the docs. It would be good however to (this may be what Dan was saying to do) create an "Additional Downloads" section with something like:

There is alternate formats of the documentation available for download at http://exim.org/docs.html.

I'm not a big fan of specific download links, or instructions for installing downloaded docs, unless there is no documentation shipped in the source tarball. In Exim's case, however, full documentation in text format is shipped with the sources.

As far as the original report in this ticket, there is already an open ticket for the Exim version update. This one is redundant, but left open for the version entity and documentation link.

comment:3 by Randy McMurchy, 18 years ago

Resolution: fixed
Status: assignedclosed

Updated the documentation links and added an 'Additional Downloads' section. Added an exim-online-docs-version entity, but it is unused now as the docs version is the same as the package version.

Note: See TracTickets for help on using tickets.