Bruce Dubbs wrote:
Okay. I'm looking for a way to show all the interdependent packages. I
was thinking of supplying the 'minimum required' packages for each
section for a functional X Window System.
The listing of internal dependencies to a single package (xorg) is
beyond the scope of the book. The only thing that *may* be necessary is
to list any drivers that need to be built to support other drivers.
We don't get into internal dependencies for KDE except for the packages
themselves that KDE places individual applications.
Gnome is split into groups where there are a set of required packages
and then we list individual packages.
X has traditionally been a single package. Let's leave it that way and
let users document internal dependencies in the wiki if they choose.
-- Bruce
Well...the outline with all the package names is in the wiki with deps
listed as {none}. I can go and delete them, but might as well save
somebody else the work. I don't think they are hurting anything. If
nobody seems to be using them by release time, then those pages can be
deleted at that time. As far as what the instructions have now, the
failsafe default is to build all packages...which I thought was made
pretty clear in the download instructions...but I don't see where a
little nudge in the right direction is a problem either. So, the
remaining question is wether to add the two libs (by name) to the Mesa
deps or no?
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
