Jeremy Huntwork wrote:
> Sorry to be critical, but I feel I should mention two things:
Don't be sorry. It is a reasonable thing to discuss.
> 1. The policy (unspoken or unwritten? I can't remember) in LFS is that
> we shouldn't use -i for sed before we build it in chapter 5, because we
> don't want to assume the host's sed has that functionality. That's why
> we've done the cp file{,.bak} && sed 's///' file.bak > file type stuff
> elsewhere in chapter 5.
If that were the policy at one time, then it should be abandoned. We now
require sed 3.02 as a part of the host requirements. According to the change
log, the in-place mechanism has been in sed since 2001-12-17. Looking at the
sed releases, that is about the time that sed-4.0 was released.
It would be much easier to change the host requirements to sed-4.0.6
(18-Mar-2003) or later rather than bend over backward to accommodate a host
that
has a package that predates the 2.6 kernel. I chose 4.0.6 as a benchmark
because that is the earliest sed-4.0 in the gnu repository.
> (A complete aside is that we could also always do a very early build of
> sed before anything else, and bash and make for that matter, like DIY
> does so that the entire build process is more robust, is buildable on
> older systems and we can use more 'modern' commands throughout the build.)
We already require bash-2.05a and make-3.79.1 or later. Are there issues with
these?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
