LFS 6.4 Book HTML

Mike McCarty Mike.McCarty at sbcglobal.net
Tue Apr 7 08:48:46 PDT 2009

Simon Geard wrote:
> On Mon, 2009-04-06 at 07:08 -0500, Mike McCarty wrote:
>> This sort of thing is standard practice with all major projects,
>> and has nothing to do with the medium in which the components
>> get realized. It has everything to do with quality assurance
>> and version control.
> Actually, I disagree - most projects don't provide errata pages, they

I suppose that's correct. The "errata pages" don't go to the
customer, they go to the support group, along with the work arounds.

> provide support releases with the defects fixed, and discourage people
> from using versions without the fixes. That's pretty much the opposite

Yes, I agree.

> of what LFS does - we expect them to follow instructions that are known
> to have problems, and to use a separate errata document to know when
> they'll run into those problems.
> If we were *really* following standard practice, we'd be applying the
> errata changes against the 6.4 book, and putting a 6.4.1 book on the
> website to replace it.

Can't dispute. You'd do a "point release".

Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!

More information about the lfs-support mailing list