#16 closed defect (invalid)
Full dependency list
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: | ras319@… |
Description
This list isn't just a list of "package a depends on package b", but also a list of "package a depends on b and c from package d"
Attachments (1)
Change History (14)
comment:1 by , 24 years ago
Status: | new → assigned |
---|
comment:2 by , 24 years ago
Owner: | changed from | to
---|---|
qa_contact: | gerard@linuxfromscratch.org → lfs-book@linuxfromscratch.org |
Status: | assigned → new |
comment:3 by , 24 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 23 years ago
comment:5 by , 23 years ago
Can I make a suggestion about this. I think that we should make this an appendix to avoid cluttering the book.
comment:6 by , 23 years ago
We've thought about that too. I was thinking about a compromise. Amongst the installation instructions we could provide a condensed list, like this (this would start in chapter 6):
Glibc depends on the following packages: fileutils, sed, bash, grep, textutils, gcc, binutils, sh-utils, make, diffutils, mawk and gzip.
That'll be only two lines (most packages are shorter and will therfore fit fine on one line).
Then in the Appendix we can provide a thorough list like this: Glibc depends on:
- mknod, touch, mkdir, mv, rm, ln, cp and chmod from the fileutils package
- sed from the sed package
- and so forth
This would mean maintaining two lists but it may not be so bad (as these kind of deps change very seldom).
So do you like this way of having a condensed list in chapters, then a thorough list in appendix?
comment:8 by , 23 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
compile time deps are present, but need to be re-checked. There are some minor mistakes here and there. library deps need added (like which lib from glibc is used, which ncurses lib, stuff like that)
besides that, any run-time dependencies (glibc/ncurses/other libs are obvious, but are there programs needed for proper running of other programs)
comment:9 by , 23 years ago
And reformat the list like this:
Bash deps: binutils: ar, ls, ld, size fileutils: chmod, cp, ls, mv, rm etc: etc
comment:10 by , 23 years ago
Seth's patch applied that reformats the dependency lists as outlined in previous comment.
comment:12 by , 22 years ago
Priority: | normal → lowest |
---|---|
Version: | 3.0-pre2 → CVS |
Update: got all them deps figured out (well the compile-time deps, there's plenty to be added in the future like which libraries exactly programs from a package use, etc, etc).
So I'll be adding this list of "package needs this and that from package b" dependencies soon, as soon as I've found a nice way of adding this without cluttering the install. instruction pages too much.