#97 closed defect (fixed)
add tree sizes and compile times to the book
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | minor | Keywords: | |
| Cc: |
Description
For both glibc and the kernel:
There should be some note that these compilations will take a *long* time.
Also there should be note of how much free space will be needed to do the
compalation.
Change History (8)
comment:1 by , 24 years ago
| Summary: | minor changes for glibc and kernel → minor changes for glibc and kernel |
|---|
comment:2 by , 24 years ago
After having given this some thought and re-reading messages from other people who have expressed interest in it, it may be a nice thing to add at least disk usage for that package and a rough compile time estimate. We don't want to add 10 different system configurations with different compile times, so we'll have to use a slightly lower end PC that most people are probably using these days. I think my Celeron 533 mhz fits nicely. It's just a rough estimate anyway...
I haven't assigned myself to this as you guys can already start working on the file size thing. Compile a package, run "du -h dirname" on the top level directory and that's the number in MB's that you will write down. Not sure where to fit this number, that can be discussed on lfs-book outside of bugzilla
comment:3 by , 24 years ago
| Summary: | minor changes for glibc and kernel → add tree sizes and compile times to the book |
|---|
Entities are now there. Gerard will close this bug when the sizes and times are added.
comment:4 by , 24 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:7 by , 24 years ago
| Version: | 3.0-pre4 → CVS |
|---|
comment:8 by , 24 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |

why do it for only 2 out of 48 packages?