Opened 14 years ago

Closed 14 years ago

#2702 closed enhancement (fixed)

clarifying the approximate build SBU number and required disk space of the package

Reported by: littlebat Owned by: lfs-book@…
Priority: normal Milestone: 6.7
Component: Book Version: SVN
Severity: trivial Keywords: wording
Cc:

Description

I found current LFS BOOK haven't clarified if the SBU number and required disk space of a package includes testsuite or not.

And, have a glance at the sections in Chapter 6, I found there are some packages marked "testsuite included" while some packages which have a testsuite but without marked "testsuite included" in the head of package section, such as: 6.25. Bison-2.4.1, 6.33. Perl-5.10.1, 6.41. Gettext-0.17, etc... but the SBU number and required disk space of these packages do include testsuite.

So I post a patch "clarify-sbu-disk_space.patch" to enhance the wording about this which includes three changes:

1, Deleted all " testsuite included" from ./packages.ent

2, Added a note into ./chapter05/binutils-pass1.xml: (the first build package in Chapter 5) The approximate build SBU number and required disk space of every package in Chapter 5 does not include testsuite.

3, Added a note into ./chapter06/linux-headers.xml (the first build package in Chapter 6): The approximate build SBU number and required disk space of every package which has testsuite in Chapter 6 includes testsuite.

Attachments (1)

clarify-sbu-disk_space.patch (6.9 KB ) - added by littlebat 14 years ago.
For fixing a trivial wording issue about clarifying the approximate build SBU number and required disk space of the package.

Download all attachments as: .zip

Change History (2)

by littlebat, 14 years ago

For fixing a trivial wording issue about clarifying the approximate build SBU number and required disk space of the package.

comment:1 by bdubbs@…, 14 years ago

Resolution: fixed
Status: newclosed

Fixed in revision 9332.

Thanks for the patch. I made some grammar changes and put the note for Chapter 6 in the introduction.

Note: See TracTickets for help on using tickets.