M.Canales.es wrote:
adjusting.xml: how the adjusting is done and the text about fixincludes
The specfile doesn't need to be dumped as it is installed by default by
gcc-3.4.x, so the 'dumpspecs' command would need to be removed and the
text above it slightly reworded to accomodate this. Given that it's not
a trivial merge, and the existing commands are well tested, I'd say
leave this one out of the branch.
gawk.xml: the two echo commands (also in chapter06)
That's due to the package upgrade, so not required for 6.1.1
gcc-pass2.xml: the fixinclude stuff and the sed to use -fomit-frame-pointer
(also in chapter06)
Similar to the adjusting.xml stuff.
bash.xml: the bash-doc package installation
Fine for 6.1.1
coreutils.xml: the pach for POSIX compatibility of echo
Only required for more modern versions of udev, so not necessary for the
branch.
devices.xml: the text about creation of /dev/null and /dev/console
Fine for 6.1.1
glibc: the text on the top about iconv and how the test suite is run
Fine for 6.1.1
iproute2: how the DB dependency is removed (a sed or a patch)
I'd prefer the sed - one less patch to maintain.
readjusting.xml: how the adjusting is done
See the comments for chapter 5's adjusting.
sed.xml: the documentation installation
Fine for 6.1.1
shadow: the two text blocks and a command related with Cracklib
Fine for 6.1.1
util-linux.xml: a patch is applied for security issues, don't should the
package be updated?
I'm not too bothered on this one. I think we preferred patches over
upgrades, simply because it we're seen to upgrade one package that may
have been seen as a precedent to upgrade others too. That reasoning
doesn't stand up really, as we upgraded perl and zlib.
That is all.
Many many thanks for this summary!
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page