Create errata page\links

[steve.crosby@…]

The current stable release does not provide a mechanism for informing users of required patches, security fixes, etc. that have been identified after a release has been made.

It is suggested that an early chapter\paragraph be created that contains information about fixes to known problems, either directly in the book text, or maintained as an HTML page on the :FS website, and the book containing a link to that page.

Further, errata should probably only be maintained for the current stable release, to reduce administration overhead of supporting older releases.

[steve.crosby@…]

Some suggested text:

As the software used in creating your LFS system is constantly updated and enhanced, new features, security warnings and fixes for problems may become available after the LFS book has been released. To check whether the instructions in this release of LFS need any changes to accomodate security or bugfixes, please visit the link below before proceeding with your build. You should note any changes shown, and apply them to the relevant section as you progress with building your LFS system.

​http://errata.linuxfromscratch.org/LFS6.1

[randy@…]

This is an excellent idea, however, I would not use the word 'errata' or 'erratum' to describe/name the page as this infers errors in the original text, which is not the case (for what is described so far in the bug).

It very well may contain any errors in the original text (as unlikely as that may be :-) ), however, it will most probably be used as is described: for additions, security enhancements and patches that came along *after* the original text was released.

There is a difference.

[archaic@…]

This could be a good use for the "generic-version" entity I proposed for the test results link here: ​http://linuxfromscratch.org/pipermail/lfs-dev/2005-June/051887.html

We could add something like:

<!ENTITY errata "​http://www.linuxfromscratch.org/lfs/view/errata-&generic-version;"/>

[archaic@…]

Regarding the use of the word "errata", it is a standard word used to describe bugfixes and other changes that happen after a text was written.

[randy@…]

Not sure about a "standard word". I think otherwise, please feel free to consult a dictionary. However, it was simply a mention, please feel to disregard.

[archaic@…]

Fixed in trunk (r6206). Awaiting merge to testing.

[manuel@…]

IMHO, an errata page is needed only for released versions. For SVN and testing versions the erratas and bugs must be fixed on the book. Then, on SVN and testing that page should be commented out, and in the website we need only errata/x.y/ dirs (or errata/x.y.html files) plus an errata/stable link pointing to the most current version.

[archaic@…]

Look at the website archives. Yesterday (or the day before) I posted a suggested html page for lfs/view/errata-svn/index.html that said errata isn't kept for testing or trunk. However, to keep this from being just one more series of things we have to do at release, it is easiest to just keep the page in and have it link to the generic-version. That way we are covered both ways.

[archaic@…]

Fixed in testing (r6207). Closing bug.